-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with server #34
Comments
Hi, I've just been improving the server management tonight. Once the server is created, you should start the server from servers status panel, after that, the cronjob will check the server status to starting it automatically in case of crash, you don't have to launch it manually from the console. The --reset option is used to stop the server in case it is running and start a new one. Upgrade your installation with The code you have pasted looks like something in hexadecimal, it is strange, I would have to check it since in the documentation I think it does not show about that. |
Coban devices use two communication protocols they call it (in,out) and the custom command you send does not respond because the default code is set to IN, you must send them the command by sms to the gps: protocol123456 18 out. Then try sending the command again and it should work. Anyway, you could reconfigure my server to test the responses. |
The server is stopped again:
|
Do you have the cron configured? Are you executing the command from console? |
I have configured cron like this
|
Sorry the previous error was wrong. I deleted the logs and and rebooted the server.
while redis is running
I tried manually restart in panel but I got this error:
seems panel wants to run with
|
Do you have configured redis in |
I belive yes
|
Cron must run as webserver user ( |
Thanks I will work on it |
Can this issue be closed? |
Yeah I think the problem is resolved. |
Hi,
Thank you for your hard work.
When I create a server, should I run it manually or not? It seems the server stops after a few hour. what is --reset ?
It seems when server is running on port 6001, it tries to run it again and I seen port is occupied error.
I sent
**,imei:868166054696190,111
command and this is the response. It wasn't like this before.1603010200010001fc03031700b78a6d6662ced60d428f8f9b4246cec7b333fe99a1a95a03da66c1ce084d20ce2447bece88dfab3f3597b592ac39288494fca50f6e38e811ca101b166ac31b0026baba130113021303c02bc02fcca9cca8c02cc030c009c013c00ac014009c009d002f0035000a0100018d3a3a0000000000180016000013747261636b696e67322e617261646f782e697200170000ff01000100000a000a00085a5a001d00170018000b0002010000230000000500050100000000000d00140012040308040401050308050501080606010201001200000033002b00295a5a000100001d002069ef802ec43f54220685733302b453c4a0ca6d1a94d59db4142c2314d4a8ff71002d00020101002b000b0a7a7a03040303030203016a6a000100001500da0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
The text was updated successfully, but these errors were encountered: