palo server is running, but not the network port

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

  • palo server is running, but not the network port

    Hi folks,
    I've tested already a couple of times the Palo server, it works rather stable. I'm really impressed from the open source Version 1 implementation. Very well done indeed. The excel plugin probably is not yet really stable or usuable by an enduser who is not an IT person. But this is in my understanding fine tuning and should be solved in the mid term ...
    So in general, great product and keep on going !!

    To come to my issue: By a sudden I'm struggling with the server on my Windows PC. It is running, the databases and dimensions are loaded (as written to the log!), but the network port is not open/served. What could be wrong? The IP address is valid, the cmputer is in the network reachable, but netstat -an does not list the port 1234 to be serverd at all.

    Any suggestions? Thanks,
    Alexander

    Windows XP with SP2

    config: <Server hostname="192.168.16.185" service="1234" protocol="TCP"></Server>

    Screenshot from netstat:
    TCP 192.168.16.185:139 0.0.0.0:0 ABHÖREN
    TCP 192.168.16.185:1027 63.208.197.26:443 HERGESTELLT
    TCP 192.168.16.185:1058 64.69.76.10:80 SCHLIESSEN_WARTEN
    TCP 192.168.16.185:1259 82.137.161.149:993 HERGESTELLT
    TCP 192.168.16.185:1337 82.137.161.149:993 HERGESTELLT
    TCP 192.168.16.185:1606 82.149.239.13:993 HERGESTELLT
    TCP 192.168.16.185:2492 198.182.235.31:2492 HERGESTELLT
    TCP 192.168.16.185:2492 198.182.235.33:2492 HERGESTELLT
    TCP 192.168.16.185:2492 198.182.235.34:2492 HERGESTELLT
    TCP 192.168.16.185:2492 198.182.235.37:2492 HERGESTELLT
    TCP 192.168.16.185:2492 198.182.235.39:2492 HERGESTELLT
    TCP 192.168.16.185:2492 198.182.235.40:2492 HERGESTELLT

    The post was edited 1 time, last by apohl ().

  • Hi!
    Did you restart the server after you made changes to the config.xml? After you restart PALOServerService the last line in palo.log should look similar to this:


    27.04.2006 10:36:40 INFO: SERVER: Listening on 192.168.16.185:1234


    Maybe you have some kind of firewall which silently blocks connections?
    Mit freundlichen Gruessen/ With kind Regards / Meilleures salutations

    Vladislav Malicevic
    VP Development & Support
    Jedox AG
  • I attach the log file

    Hi Vladislav,
    Just talked to KR ...

    No Firewall, no networking issues ... I checked again the log and my impression is, there is a problem with the databases. Should I delete them? I enclose the last log entries, should be the information you require.

    Cheers, Alexander

    PS: I couldn't upload the file, so I paste it to this forum entry!

    INFO: LOG: changed log file to "palo.log"
    INFO: loading authentication configuration: ".\auth.xml"
    INFO: loading root: ".\root.xml"
    INFO: loading root: configuration file not present - loading any available databases
    INFO: loading database: ".\Demo\Demo.xml"
    INFO: loading database: configuration file not present - loading any available dimensions and cubes
    INFO: processing dimension: "Datatypes"
    INFO: loading dimension: ".\Demo\RGF0YXR5cGVz.dimension.xml"
    INFO: using dimension log file: ".\Demo\RGF0YXR5cGVz.dimension.log"
    INFO: processing dimension: "Months"
    INFO: loading dimension: ".\Demo\TW9udGhz.dimension.xml"
    INFO: using dimension log file: ".\Demo\TW9udGhz.dimension.log"
    INFO: processing dimension: "Measures"
    INFO: loading dimension: ".\Demo\TWVhc3VyZXM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\TWVhc3VyZXM=.dimension.log"
    INFO: processing dimension: "Products"
    INFO: loading dimension: ".\Demo\UHJvZHVjdHM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\UHJvZHVjdHM=.dimension.log"
    INFO: processing dimension: "Regions"
    INFO: loading dimension: ".\Demo\UmVnaW9ucw==.dimension.xml"
    INFO: using dimension log file: ".\Demo\UmVnaW9ucw==.dimension.log"
    INFO: processing dimension: "Years"
    INFO: loading dimension: ".\Demo\WWVhcnM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\WWVhcnM=.dimension.log"
    INFO: loading cube: ".\Demo\U2FsZXM=.cube.xml"
    INFO: loading cube data file: ".\Demo\U2FsZXM=.cube.data"
    INFO: using cube log file: ".\Demo\U2FsZXM=.cube.log"
    INFO: using dimension log file: ".\Demo\UHJvZHVjdHM=.dimension.log"
    INFO: using dimension log file: ".\Demo\UmVnaW9ucw==.dimension.log"
    INFO: using dimension log file: ".\Demo\TW9udGhz.dimension.log"
    INFO: using dimension log file: ".\Demo\WWVhcnM=.dimension.log"
    INFO: using dimension log file: ".\Demo\RGF0YXR5cGVz.dimension.log"
    INFO: using dimension log file: ".\Demo\TWVhc3VyZXM=.dimension.log"
    INFO: synchronizing storage ids
    INFO: loading database: ".\EOS\EOS.xml"
    INFO: loading database: configuration file not present - loading any available dimensions and cubes
    INFO: processing dimension: "GJ Beginn März"
    INFO: loading dimension: ".\EOS\R0ogQmVnaW5uIE3DpHJ6.dimension.xml"
    INFO: using dimension log file: ".\EOS\R0ogQmVnaW5uIE3DpHJ6.dimension.log"
    INFO: processing dimension: "Konten"
    INFO: loading dimension: ".\EOS\S29udGVu.dimension.xml"
    INFO: using dimension log file: ".\EOS\S29udGVu.dimension.log"
    INFO: saving dimension: ".\EOS\S29udGVu.dimension.xml"
    INFO: SERVICE CONTROL: control request
    INFO: SERVICE CONTROL: setting service status
    INFO: SERVICE CONTROL: stopping...
    INFO: SHUTDOWN: locking root...
    INFO: SHUTDOWN: anouncing shutdown...
    INFO: SHUTDOWN: invoking killer...
    INFO: LOG: changed log file to "palo.log"
    INFO: loading authentication configuration: ".\auth.xml"
    INFO: loading root: ".\root.xml"
    INFO: loading root: configuration file not present - loading any available databases
    INFO: loading database: ".\Demo\Demo.xml"
    INFO: loading database: configuration file not present - loading any available dimensions and cubes
    INFO: processing dimension: "Datatypes"
    INFO: loading dimension: ".\Demo\RGF0YXR5cGVz.dimension.xml"
    INFO: using dimension log file: ".\Demo\RGF0YXR5cGVz.dimension.log"
    INFO: processing dimension: "Months"
    INFO: loading dimension: ".\Demo\TW9udGhz.dimension.xml"
    INFO: using dimension log file: ".\Demo\TW9udGhz.dimension.log"
    INFO: processing dimension: "Measures"
    INFO: loading dimension: ".\Demo\TWVhc3VyZXM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\TWVhc3VyZXM=.dimension.log"
    INFO: processing dimension: "Products"
    INFO: loading dimension: ".\Demo\UHJvZHVjdHM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\UHJvZHVjdHM=.dimension.log"
    INFO: processing dimension: "Regions"
    INFO: loading dimension: ".\Demo\UmVnaW9ucw==.dimension.xml"
    INFO: using dimension log file: ".\Demo\UmVnaW9ucw==.dimension.log"
    INFO: processing dimension: "Years"
    INFO: loading dimension: ".\Demo\WWVhcnM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\WWVhcnM=.dimension.log"
    INFO: loading cube: ".\Demo\U2FsZXM=.cube.xml"
    INFO: loading cube data file: ".\Demo\U2FsZXM=.cube.data"
    INFO: using cube log file: ".\Demo\U2FsZXM=.cube.log"
    INFO: using dimension log file: ".\Demo\UHJvZHVjdHM=.dimension.log"
    INFO: using dimension log file: ".\Demo\UmVnaW9ucw==.dimension.log"
    INFO: using dimension log file: ".\Demo\TW9udGhz.dimension.log"
    INFO: using dimension log file: ".\Demo\WWVhcnM=.dimension.log"
    INFO: using dimension log file: ".\Demo\RGF0YXR5cGVz.dimension.log"
    INFO: using dimension log file: ".\Demo\TWVhc3VyZXM=.dimension.log"
    INFO: synchronizing storage ids
    INFO: loading database: ".\EOS\EOS.xml"
    INFO: loading database: configuration file not present - loading any available dimensions and cubes
    INFO: processing dimension: "GJ Beginn März"
    INFO: loading dimension: ".\EOS\R0ogQmVnaW5uIE3DpHJ6.dimension.xml"
    INFO: using dimension log file: ".\EOS\R0ogQmVnaW5uIE3DpHJ6.dimension.log"
    INFO: processing dimension: "Konten"
    INFO: loading dimension: ".\EOS\S29udGVu.dimension.xml"
    INFO: using dimension log file: ".\EOS\S29udGVu.dimension.log"
    INFO: processing dimension: "Jahr=GJ"
    INFO: loading dimension: ".\EOS\SmFocj1HSg==.dimension.xml"
    INFO: using dimension log file: ".\EOS\SmFocj1HSg==.dimension.log"
    INFO: saving dimension: ".\EOS\SmFocj1HSg==.dimension.xml"
    INFO: SERVICE CONTROL: control request
    INFO: SERVICE CONTROL: setting service status
    INFO: SERVICE CONTROL: stopping...
    INFO: SHUTDOWN: locking root...
    INFO: SHUTDOWN: anouncing shutdown...
    INFO: SHUTDOWN: invoking killer...
    INFO: LOG: changed log file to "palo.log"
    INFO: loading authentication configuration: ".\auth.xml"
    INFO: loading root: ".\root.xml"
    INFO: loading root: configuration file not present - loading any available databases
    INFO: loading database: ".\Demo\Demo.xml"
    INFO: loading database: configuration file not present - loading any available dimensions and cubes
    INFO: processing dimension: "Datatypes"
    INFO: loading dimension: ".\Demo\RGF0YXR5cGVz.dimension.xml"
    INFO: using dimension log file: ".\Demo\RGF0YXR5cGVz.dimension.log"
    INFO: processing dimension: "Months"
    INFO: loading dimension: ".\Demo\TW9udGhz.dimension.xml"
    INFO: using dimension log file: ".\Demo\TW9udGhz.dimension.log"
    INFO: processing dimension: "Measures"
    INFO: loading dimension: ".\Demo\TWVhc3VyZXM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\TWVhc3VyZXM=.dimension.log"
    INFO: processing dimension: "Products"
    INFO: loading dimension: ".\Demo\UHJvZHVjdHM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\UHJvZHVjdHM=.dimension.log"
    INFO: processing dimension: "Regions"
    INFO: loading dimension: ".\Demo\UmVnaW9ucw==.dimension.xml"
    INFO: using dimension log file: ".\Demo\UmVnaW9ucw==.dimension.log"
    INFO: processing dimension: "Years"
    INFO: loading dimension: ".\Demo\WWVhcnM=.dimension.xml"
    INFO: using dimension log file: ".\Demo\WWVhcnM=.dimension.log"
    INFO: loading cube: ".\Demo\U2FsZXM=.cube.xml"
    INFO: loading cube data file: ".\Demo\U2FsZXM=.cube.data"
    INFO: using cube log file: ".\Demo\U2FsZXM=.cube.log"
    INFO: using dimension log file: ".\Demo\UHJvZHVjdHM=.dimension.log"
    INFO: using dimension log file: ".\Demo\UmVnaW9ucw==.dimension.log"
    INFO: using dimension log file: ".\Demo\TW9udGhz.dimension.log"
    INFO: using dimension log file: ".\Demo\WWVhcnM=.dimension.log"
    INFO: using dimension log file: ".\Demo\RGF0YXR5cGVz.dimension.log"
    INFO: using dimension log file: ".\Demo\TWVhc3VyZXM=.dimension.log"
    INFO: synchronizing storage ids
    INFO: loading database: ".\EOS\EOS.xml"
    INFO: loading database: configuration file not present - loading any available dimensions and cubes
    INFO: processing dimension: "GJ Beginn März"
    INFO: loading dimension: ".\EOS\R0ogQmVnaW5uIE3DpHJ6.dimension.xml"
    INFO: using dimension log file: ".\EOS\R0ogQmVnaW5uIE3DpHJ6.dimension.log"
    INFO: processing dimension: "Konten"
    INFO: loading dimension: ".\EOS\S29udGVu.dimension.xml"
    INFO: using dimension log file: ".\EOS\S29udGVu.dimension.log"
    INFO: processing dimension: "Jahr=GJ"
    INFO: loading dimension: ".\EOS\SmFocj1HSg==.dimension.xml"
    INFO: using dimension log file: ".\EOS\SmFocj1HSg==.dimension.log"
    INFO: loading cube: ".\EOS\R3VW.cube.xml"
    INFO: loading cube data file: ".\EOS\R3VW.cube.data"
    INFO: using cube log file: ".\EOS\R3VW.cube.log"
    INFO: using dimension log file: ".\EOS\S29udGVu.dimension.log"
    INFO: synchronizing storage ids
    INFO: saving cube data file: ".\EOS\R3VW.cube.data"
  • RE: I attach the log file

    Hi!
    Seams like you have a huge database/slow machine … starting Palo server takes some time … you can check in Task Manager – during the start stage palo.exe process will do some heavy load on you CPU … when the loading stage is over … CPU usage will go down … and the server should become available – start listening on the configured port … like I said in my previous post … once the server is started … last line in the palo.log should look like:

    27.04.2006 10:36:40 INFO: SERVER: Listening on 192.168.16.185:1234



    Can you access the server on a localhost?
    Mit freundlichen Gruessen/ With kind Regards / Meilleures salutations

    Vladislav Malicevic
    VP Development & Support
    Jedox AG
  • RE: I attach the log file

    ... yes, yes I got your message/hint - don't worry ...
    But the cube was not big at all. I gave this pc more than an hour to start/load. But no chance.
    Therefor I deleted in the meantime this cube and now it starts again smoothlessly. But this is not really a solution. It's just a workaround. My impression was and is, the database was corrupt. The same database on my notebook started in less than half a minute.

    Therefor two remarks and questions:
    [list=1]
    How to check the integrity or how to repair a broken database?
    Why are not time stamps in the log? Ok with Linux I understand you could pipe the messages to a kind of syslogger. But nevertheless, I'm not sure, you really had this in mind.
    [/list=1]

    Cheers, Alexander[/list]
  • RE: I attach the log file

    Hi!
    Theoretically ... corruptions should never happen … when copying data files from one system to another … you should make sure the changes you made are committed (stop server; eventually start it again to make sure log changes are written; stop server) … use some good archiving tool to store data directories … copy/unpack archive to target machine … start server …
    As you can see from my previous post … server version I’m using does write timestamp … I’m not sure if this code is committed to source code which is available for download … I can check this … and make sure next release has it.
    Mit freundlichen Gruessen/ With kind Regards / Meilleures salutations

    Vladislav Malicevic
    VP Development & Support
    Jedox AG
  • RE: I attach the log file

    ....thanks for your feedback - as usual :)
    In both binary versions, Linux and Windows there are no time stamps. I've installed it on 4 different pc's in the meantime and you can take it as granted, I didn't recompile the code. I'm not a system gick :)
    Cheers, Alexander