@Damian since I see no chkconfig line I'm going to assume that's a no. He did install it as a service so it does depend whether openstatus-client does that for you, but I know similar software requires you manually add it to startup.

For openstatus-client on Debian/Ubuntu, you should use the openstatus-client package from the repo. It will grab all of the dependencies and set it up to start at boot automatically. You'll just need to edit the /etc/openstatus/openstatus-client.conf file.

@PAD said: Write a script to do it for you, duh.
You get cookie points when you automate stuff.

I actually realized this topic is about OpenStatus-Server but I figured having a script to install the client would actually be more useful since you only need to install the server once but do many client installs (especially if you have a bunch of LEBs like me).

@NHRoel That 5 minute distance is usually enough to cause Openstatus to say a server is offline, which is why I changed all instances from "data['time']" to "time()" in the /usr/bin/openstatus-server file

This should be unrelated though, as there shouldn't be a 6 hour time difference. Usually that means a timezone is misconfigured or something. What happens if you remove and readd the server?

Make sure you aren't running multiple instances of openstatus-server, as that can cause your issue when trying to debug.

@NHRoel looks like there's already an openstatus-server running with PID 565 which is why you get the couldn't listen error when you ran it on the command line with -d. Stop it with the init script if you want to run it in debug mode on the command line or restart it with the init script.

@NHRoel It runs a time comparison to what the time currently is. Both scripts seem to use slightly different methods of getting time, which could make up for the error. If you read up to my previous reply you'll see the best way to actually fix the issue, which is relying on the host time.

@Night Would you be kind enough to share your edited file? I changed as you have asked and this is what I get,
openstatus-server
File "/usr/bin/openstatus-server", line 236
roundedtime = int(time() // 60) * 60)

Hi everybody! I've just pushed out version 0.6.6 to the repo, which should solve the issues that you see when the time on the clients doesn't match the time on the server. Instead of relying on the timestamp from the client, the server now stores the local timestamp. If you're using the Debian repo, you should be able to just do apt-get update && apt-get upgrade. Otherwise, you can grab the latest openstatus-server file here. Let me know if you experience any other problems :)

Oops…
Trac detected an internal error:
OSError: [Errno 24] Too many open files
There was an internal error in Trac. It is recommended that you inform your local Trac administrator and give him all the information he needs to reproduce the issue.