re: W/R: W010024111
I'm unable to start a Progress server on this system.
I'm running 9.1A22 on Solaris 2.7.
I can create a DB, load it, and run it single-user.
But when I try to start a server, it fails - purportedly on a
hostname lookup.
For instance, if I run
prodb demo empty
proserve demo
I get the following lines in the .lg file.
14:19:47 BROKER 0: demo.lk: HOSTNAME is myhostname.mydept.company.com, expected myhostname.mydept.company.comjdemo.lk. (4192)
14:19:47 BROKER 0: demo.lk is not a valid .lk file for this server. (4196)14:19:47 BROKER 0: demo.lk is not a valid .lk file for this server. (4196)
Then the server shuts down.
Some notes:
1) The hostnames have been changed above (for security). I kept the
lengths and the number of dots the same, though.
2) The DNS is almost certainly correct. I'd be happy to review it again
if there are any questions about it though.
3) The characters following the HOSTNAME above and the stuff which follows
changes occasionally. It really looks like a string that's not null-
terminated.
Has anyone seen this? In an effort to narrow down the source of the problem,
I'd like to check the the lock file that is created. Does anyone
know the .lk file format?
"Phil Freed" wrote:
>
>re: W/R: W010024111
>
>I'm unable to start a Progress server on this system.
>I'm running 9.1A22 on Solaris 2.7.
>
>I can create a DB, load it, and run it single-user.
>But when I try to start a server, it fails - purportedly
>on a
>hostname lookup.
>
>For instance, if I run
prodb demo empty
proserve demo
>
>I get the following lines in the .lg file.
>14:19:47 BROKER 0: demo.lk: HOSTNAME is myhostname.mydept.company.com,
>expected myhostname.mydept.company.comjdemo.lk. (4192)
>14:19:47 BROKER 0: demo.lk is not a valid .lk file for
>this server. (4196)14:19:47 BROKER 0: demo.lk is not
>a valid .lk file for this server. (4196)
>
>Then the server shuts down.
>
>Some notes:
>1) The hostnames have been changed above (for security).
I kept the
lengths and the number of dots the same, though.
>2) The DNS is almost certainly correct. I'd be happy
>to review it again
if there are any questions about it though.
>3) The characters following the HOSTNAME above and the
>stuff which follows
changes occasionally. It really looks like a string
>that's not null-
terminated.
>
>Has anyone seen this? In an effort to narrow down the
>source of the problem,
>I'd like to check the the lock file that is created.
>Does anyone
>know the .lk file format?
>
The format of the dbname.lk file is data, but you can view the information held in this file. The important part of this file is that it contains the dtails related to the host when you started the database. If you have changed the name of your host, the databases should have been shut down prior to this.