wwhry

Suggestions for PinBotAI (aka PinBotAI 4.0)

Recommended Posts

I have changed my VPS, bought a new one. I think this is the reason. But please guide what shall I do now? I have moved the whole folder to new VPS (unzipped) And this problem is occuring now.

Share this post


Link to post
Share on other sites

Resolved the login issue. Have redone it all and its working now. (redone=unzipped and set the accounts again)


Thanks

  • Like 1

Share this post


Link to post
Share on other sites
3 hours ago, wwhry said:

Resolved the login issue. Have redone it all and its working now. (redone=unzipped and set the accounts again)


Thanks

I am not exactly sure what caused all these issues on your side. But I'm glad all is resolved now :) Thanks for keeping me updated!

Share this post


Link to post
Share on other sites

@ilya

 

Please do something with the memory issue.
PinBotAI is eating up 95% of my CPU on my VPS. I had this problem on old VPS then I moved to new one and having same issue.
Please why its happening. Because of this (I think) most of my accounts stop autopilot. (don't know exactly but a guess)

Anyway, my whole VPS is suffering from this javaw.exe its eating 95% of CPU.

Share this post


Link to post
Share on other sites
On 11/6/2017 at 6:12 AM, wwhry said:

@ilya

 

Please do something with the memory issue.
PinBotAI is eating up 95% of my CPU on my VPS. I had this problem on old VPS then I moved to new one and having same issue.
Please why its happening. Because of this (I think) most of my accounts stop autopilot. (don't know exactly but a guess)

Anyway, my whole VPS is suffering from this javaw.exe its eating 95% of CPU.

The CPU usage highly depends on which actions are being performed by PinBot and more importantly how many of them.
How many accounts are you running at the same time?

 

Share this post


Link to post
Share on other sites
6 hours ago, ilya said:

The CPU usage highly depends on which actions are being performed by PinBot and more importantly how many of them.
How many accounts are you running at the same time?

 

I"m running less than 40 accounts right now. And if this bot can't handle just 40 or 50 accounts, then I think its a loss.
I'm running followliker for instagram with 100+ accounts without any issue, without any CPU memory problem etc.

I have tried your bot on different VPSes but getting same memory issue everywhere mate.

Finally I have stopped using it for a few days because its giving nothing more than trouble, in multiple aspects.

Eating 100% CPU memory

No bulk configuration is available at all. (If you are bulk accounts user, you'll face lot of pain)

---------

Kind of hopeless right now, sorry to say, but I'm having this feeler!
Though I wished to see this bot at the top of others, but your support is getting very slow day by day.....Just like you can see when I had posted this issue and when you have answered it. (Still other issues mentioned in this thread aren't answered yet, not from me, but from other users as well)

Share this post


Link to post
Share on other sites

Here comes something new:
It happens when I'm trying to delete the accounts.
 

Quote

Mon Jun 19 08:08:53 EDT 2017

#117 DAL error: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: org.h2.jdbc.JdbcSQLException: Database may be already in use: null. Possible solutions: close all other connection(s); use the server mode [90020-193]
Error Code: 90020
Query: UpdateObjectQuery(domain.account.meta.AccountMeta@6725df)
---
exception stacktrace:
javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: org.h2.jdbc.JdbcSQLException: Database may be already in use: null. Possible solutions: close all other connection(s); use the server mode [90020-193]
Error Code: 90020
Query: UpdateObjectQuery(domain.account.meta.AccountMeta@6725df)
    at org.eclipse.persistence.internal.jpa.EntityManagerImpl.flush(EntityManagerImpl.java:868)
    at DAL.Dal.deleteAccountWrap(Dal.java:130)
    at stages.AccountSelectorController.mnuDeleteAcc_click(AccountSelectorController.java:640)
    at stages.AccountSelectorController.lambda$initContextMenu$12(AccountSelectorController.java:377)
    at com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(CompositeEventHandler.java:86)
    at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:238)
    at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:191)
    at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:58)
    at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
    at com.sun.javafx.event.EventUtil.fireEventImpl(EventUtil.java:74)
    at com.sun.javafx.event.EventUtil.fireEvent(EventUtil.java:49)
    at javafx.event.Event.fireEvent(Event.java:198)
    at javafx.scene.control.MenuItem.fire(MenuItem.java:462)
    at com.sun.javafx.scene.control.skin.ContextMenuContent$MenuItemContainer.doSelect(ContextMenuContent.java:1405)
    at com.sun.javafx.scene.control.skin.ContextMenuContent$MenuItemContainer.lambda$createChildren$343(ContextMenuContent.java:1358)
    at com.sun.javafx.event.CompositeEventHandler$NormalEventHandlerRecord.handleBubblingEvent(CompositeEventHandler.java:218)
    at com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(CompositeEventHandler.java:80)
    at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:238)
    at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:191)
    at com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(CompositeEventDispatcher.java:59)
    at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:58)
    at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
    at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56)
    at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
    at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56)
    at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
    at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56)
    at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
    at com.sun.javafx.event.EventUtil.fireEventImpl(EventUtil.java:74)
    at com.sun.javafx.event.EventUtil.fireEvent(EventUtil.java:54)
    at javafx.event.Event.fireEvent(Event.java:198)
    at javafx.scene.Scene$MouseHandler.process(Scene.java:3757)
    at javafx.scene.Scene$MouseHandler.access$1500(Scene.java:3485)
    at javafx.scene.Scene.impl_processMouseEvent(Scene.java:1762)
    at javafx.scene.Scene$ScenePeerListener.mouseEvent(Scene.java:2494)
    at com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(GlassViewEventHandler.java:381)
    at com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(GlassViewEventHandler.java:295)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.javafx.tk.quantum.GlassViewEventHandler.lambda$handleMouseEvent$354(GlassViewEventHandler.java:417)
    at com.sun.javafx.tk.quantum.QuantumToolkit.runWithoutRenderLock(QuantumToolkit.java:389)
    at com.sun.javafx.tk.quantum.GlassViewEventHandler.handleMouseEvent(GlassViewEventHandler.java:416)
    at com.sun.glass.ui.View.handleMouseEvent(View.java:555)
    at com.sun.glass.ui.View.notifyMouse(View.java:937)
    at com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
    at com.sun.glass.ui.win.WinApplication.lambda$null$148(WinApplication.java:191)
    at java.lang.Thread.run(Unknown Source)
Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: org.h2.jdbc.JdbcSQLException: Database may be already in use: null. Possible solutions: close all other connection(s); use the server mode [90020-193]
Error Code: 90020
Query: UpdateObjectQuery(domain.account.meta.AccountMeta@6725df)
    at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
    at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:326)
    at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:138)
    at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
    at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:346)
    at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:307)
    at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connect(DatasourceAccessor.java:434)
    at org.eclipse.persistence.sessions.server.ConnectionPool.buildConnection(ConnectionPool.java:217)
    at org.eclipse.persistence.sessions.server.ConnectionPool.acquireConnection(ConnectionPool.java:136)
    at org.eclipse.persistence.sessions.server.ServerSession.acquireClientConnection(ServerSession.java:249)
    at org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:269)
    at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:242)
    at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
    at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:797)
    at org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:435)
    at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1079)
    at org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
    at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:301)
    at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
    at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:899)
    at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:798)
    at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
    at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2896)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1804)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1786)
    at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1737)
    at org.eclipse.persistence.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:267)
    at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsForClassWithChangeSet(CommitManager.java:192)
    at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:138)
    at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:4207)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1441)
    at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithPreBuiltChangeSet(UnitOfWorkImpl.java:1587)
    at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.writeChanges(RepeatableWriteUnitOfWork.java:452)
    at org.eclipse.persistence.internal.jpa.EntityManagerImpl.flush(EntityManagerImpl.java:863)
    ... 45 more
Caused by: org.h2.jdbc.JdbcSQLException: Database may be already in use: null. Possible solutions: close all other connection(s); use the server mode [90020-193]
    at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
    at org.h2.message.DbException.get(DbException.java:168)
    at org.h2.mvstore.db.MVTableEngine$Store.convertIllegalStateException(MVTableEngine.java:187)
    at org.h2.mvstore.db.MVTableEngine$Store.open(MVTableEngine.java:167)
    at org.h2.mvstore.db.MVTableEngine.init(MVTableEngine.java:99)
    at org.h2.engine.Database.getPageStore(Database.java:2468)
    at org.h2.engine.Database.open(Database.java:695)
    at org.h2.engine.Database.openDatabase(Database.java:273)
    at org.h2.engine.Database.<init>(Database.java:267)
    at org.h2.engine.Engine.openSession(Engine.java:64)
    at org.h2.engine.Engine.openSession(Engine.java:176)
    at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)
    at org.h2.engine.Engine.createSession(Engine.java:137)
    at org.h2.engine.Engine.createSession(Engine.java:27)
    at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:349)
    at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:115)
    at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:99)
    at org.h2.Driver.connect(Driver.java:69)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:98)
    ... 77 more
Caused by: java.lang.IllegalStateException: The file is locked: nio:C:/Users/Administrator/Desktop/pinbotai4/db/db.mv.db [1.4.193/7]
    at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:765)
    at org.h2.mvstore.FileStore.open(FileStore.java:168)
    at org.h2.mvstore.MVStore.<init>(MVStore.java:348)
    at org.h2.mvstore.MVStore$Builder.open(MVStore.java:2923)
    at org.h2.mvstore.db.MVTableEngine$Store.open(MVTableEngine.java:154)
    ... 94 more
Caused by: java.nio.channels.OverlappingFileLockException
    at sun.nio.ch.SharedFileLockTable.checkList(Unknown Source)
    at sun.nio.ch.SharedFileLockTable.add(Unknown Source)
    at sun.nio.ch.FileChannelImpl.tryLock(Unknown Source)
    at org.h2.store.fs.FileNio.tryLock(FilePathNio.java:121)
    at java.nio.channels.FileChannel.tryLock(Unknown Source)
    at org.h2.mvstore.FileStore.open(FileStore.java:165)
    ... 97 more

 

 

Share this post


Link to post
Share on other sites
13 hours ago, asphero said:

I think ilya spent lots of time on development of instaQ.

Hope he can spend some time here.

This is FACT!
And its leading towards something not good. Because, I'm sort of fed up right now, with PinBotAi thing. Because its not for bulk accounts, as far as I have understand.

And by bulk, I don't mean 1 or 2 or 10 accounts, I'm talking about 50/100/more accounts.

Now if someone says, why you need this much accounts? Well, I do need, for my stuff to work. This is what I have purchased this software for, otherwise I have my own workers at my office, who can handle 10 to 20 accounts each day manually.

........No one is listening to our issues these days........I think at BlackHatWorld, we'll be heard!!!

Share this post


Link to post
Share on other sites

@wwhry

 

Do you use these satellite accounts to promote main account?Any strategy for Pinterest update these days?  It is hard to get traffic from to me, could you give me some tips?

 

Share this post


Link to post
Share on other sites

Can you make settings section for the autopilot? I want to adjust the autopilot because the spam level is very much bellow the threshold. If this is a spamming AI bot, make it look like a spamming bot :) Anyway, the app works great so far, keep up the good work and don't forget that you've made a SPAM machine xD

Edited by apache

Share this post


Link to post
Share on other sites

@apache @asphero @Hehe @wwhry

Thank you for your feedback and support guys!
I fully understand your problems and am looking into it.

In the coming two weeks I am able to devote all my time to PinBotAI, hopefully it's enough to fix all current problems.

@wwhry would it be possible to schedule a teamviewer session so I can access your VPS and investigate the CPU problem?

Thanks! :)

  • Like 1

Share this post


Link to post
Share on other sites
On 6/29/2017 at 3:59 PM, ilya said:

@apache @asphero @Hehe @wwhry

Thank you for your feedback and support guys!
I fully understand your problems and am looking into it.

In the coming two weeks I am able to devote all my time to PinBotAI, hopefully it's enough to fix all current problems.

@wwhry would it be possible to schedule a teamviewer session so I can access your VPS and investigate the CPU problem?

Thanks! :)

Okay, will PM you!

Share this post


Link to post
Share on other sites

Bug Report #1: Entering Autopilot Start times using the keyboard results in the times not changing. I imagine this is because there isn't a key-down event registering that the times are being changed. When you enter the time manually, then use the up or down arrows, this then seems to fire off an event that updates the time variable.

Bug Report #2: In the Autopilot start time boxes, the up arrow doesn't work when you are clicked on the minute section of the time.

  • Like 1

Share this post


Link to post
Share on other sites

Getting the following error after recent update:

 

Tue Jul 25 13:59:56 EDT 2017

#AEDL: error during login process: P#117
---
exception stacktrace:
AI.helpers.Exceptions.MiscAIException: P#117
	at AI.scraping.Scraper.processResponse(Scraper.java:186)
	at AI.scraping.Scraper.run(Scraper.java:100)
	at domain.pinterest.ScrapeServices.ScrapeBoards(ScrapeServices.java:52)
	at domain.account.AccountServices.refreshBoards(AccountServices.java:200)
	at Runnables.AccountDoLoginFull.__run(AccountDoLoginFull.java:46)
	at Runnables.AbortRunnable.run(AbortRunnable.java:64)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

 

Share this post


Link to post
Share on other sites

Most of the issues are resolved but still you aren't looking into bulk import of accounts settings.
And
a function to create the keywords same like the board names with single click.

Means, I click a button "Get Keywords From Boards" and all the boards names are pasted in the "keywords" box on right side for every board (1 board name = 1 keyword in right side panel)

Also, if I want to set same PROMO url for all the boards, I could do it with single click.

Share this post


Link to post
Share on other sites

Exactly, it would be really great if we could finally get some of the upcomming features that are in the list..

 

Share this post


Link to post
Share on other sites

Here comes another update of PinBotAi 4

And nothing is updated in change log thread.........Don't know what is changed now!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now