Wiki Forum Sign up! Explore Home

Not signed in (Sign In)

LiveSearch

Welcome, Guest

Want to take part in these discussions? Sign in if you have an account, or apply for one below

Vanilla 1.1.2 is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthorurchin
    • CommentTimeFeb 7th 2008
     permalink
    I notice that the push_server dies after a while.

    Is there any plan to upgrade juggernaut? I notice on their site they seem to have done a total rewrite.

    ---
    • CommentAuthoradmin
    • CommentTimeFeb 7th 2008
     permalink
    Pretty hard to tell what's wrong if you don't let me see the errors. :-) Mine is running for months at a time, so it's working fine.

    -- Erlend
    • CommentAuthorurchin
    • CommentTimeFeb 7th 2008 edited
     permalink
    There are no errors is seems to just stop :( I am running ubuntu 7.10.

    I use setsid ruby script/push_server to start it up.

    The reason I asked about the upgrade was I saw this message:

    I will investigate more today.

    --
    • CommentAuthoradmin
    • CommentTimeFeb 7th 2008
     permalink
    Stop as in stop, or stop as in die? Could you try leaving it running in a terminal without logging out from your server and see if it keeps running then? How long does it take?

    The posts you linked to are about the client timing out, not the server dying.

    -- Erlend
    • CommentAuthordarkpollo
    • CommentTimeFeb 7th 2008
     permalink
    Mine is having the same problem, i thought that was my server, but i will check it tonight and tell you the error.
    Also i cannot make it work outside the local LAN, but that is another problem. :D
    • CommentAuthorurchin
    • CommentTimeFeb 7th 2008
     permalink
    This issue was reported before with a solution here

    >>The posts you linked to are about the client timing out
    Yes I see, however I was referring more to the rewrite of the Juggernaut code, If we had the latest version in ClockingIT then we could enlist the aid of the developer or perhaps the problem might no longer exist. :)

    The stop is random. I am monitoring it in a terminal session at the moment.

    --
    • CommentAuthoradmin
    • CommentTimeFeb 7th 2008
     permalink
    You killing the push_deamon by not running it in the background isn't really a problem with the push_daemon. :-)

    -- Erlend