PALOServerService keeps stopping

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • PALOServerService keeps stopping

    I've just installed PALO for the first time. PALO Server Manager allows me to start the server, but it keeps stopping after about five seconds of up-time.

    My palo.ini file is set to all defaults:

    Source Code

    1. cache-barrier 5000
    2. user-login
    3. verbose info
    4. log "C:\Program Files\Palo\Log\PaloServer.log"
    5. http "127.0.0.1" 7777
    6. template-directory "C:\Program Files\Palo\Api"


    I am working with a company firewall and I suppose this may be the problem. Any ideas where to start and what to try? Thanks for your help; I'm a complete newbie in case it's not obvious. :)
  • Dominik,

    Thank you! I do not have admin privileges on my computer, and I knew that could also be a challenge. I had an admin install Palo, and indeed the log file for that event looks pretty successful:

    Source Code

    1. 2009-01-16 21:46:29 INFO: starting Palo 2.5.0 (3627)
    2. 2009-01-16 21:46:29 INFO: http port '7777' on address '127.0.0.1' open
    3. 2009-01-16 21:46:29 INFO: registered system database 'System'
    4. 2009-01-16 21:46:29 INFO: registered database 'Demo'
    5. 2009-01-16 21:46:29 INFO: registered database 'Biker'
    6. 2009-01-16 21:46:29 INFO: system database not yet loaded, loading now
    7. 2009-01-16 21:46:29 INFO: auto loading database 'Demo'
    8. 2009-01-16 21:46:29 INFO: created CubeDimension
    9. 2009-01-16 21:46:37 INFO: setting client cache type to 0
    10. 2009-01-16 21:46:37 INFO: setting hide elements to 0
    11. 2009-01-16 21:46:37 INFO: auto loading database 'Biker'
    12. 2009-01-16 21:46:37 INFO: created CubeDimension
    13. 2009-01-16 21:46:43 INFO: setting client cache type to 0
    14. 2009-01-16 21:46:43 INFO: setting hide elements to 0
    15. 2009-01-16 21:46:43 INFO: rebuilding all markers
    16. 2009-01-16 21:46:43 INFO: starting to listen
    17. 2009-01-16 21:46:56 INFO: handled signal 2
    18. 2009-01-16 21:47:11 INFO: handled signal 2
    19. 2009-01-16 21:47:27 INFO: handled signal 2
    20. 2009-01-16 21:47:27 INFO: begin shutdown of service
    21. 2009-01-16 21:47:27 INFO: beginning shutdown sequence
    22. 2009-01-16 21:47:28 INFO: listener sockets closed
    23. 2009-01-16 21:47:31 INFO: read/write sockets closed
    24. 2009-01-16 21:47:31 INFO: finished.
    Display All


    Afterward, using my own sign-on, I get the same seven-line pattern each time I start the Server Manager.

    Source Code

    1. 2009-01-19 21:54:25 INFO: starting Palo 2.5.0 (3627)
    2. 2009-01-19 21:54:26 INFO: http port '7777' on address '127.0.0.1' open
    3. 2009-01-19 21:54:26 WARNING: using temp file for server
    4. 2009-01-19 21:54:26 WARNING: could not read from file './palo.csv' (Permission denied)
    5. 2009-01-19 21:54:26 WARNING: failed to load server 'could not open file for reading' (file name: './palo.csv')
    6. 2009-01-19 21:54:26 ERROR: cannot rename server file: 'File exists
    7. 2009-01-19 21:54:26 ERROR: please check the underlying file system for errors


    I don't foresee changing my permissions any time soon, but maybe I can move some files and change the ini file. Is that an avenue worth pursuing? If so, can you give me any specific pointers?

    Many thanks,
    Benjamin