Corrupted files on system shutdown

bridged with qdn.public.qnxrtp.applications
Post Reply
Geoff

Corrupted files on system shutdown

Post by Geoff » Fri Nov 29, 2002 6:57 am

On my QNX6 box I run a number of standard servers (apache, NTP, Samba).
All of them maintain log files. Both Apache and Samba maintaing lock
files. If I reboot the machine without expressly shutting each one of
these servers down, they won't restart when the machine comes back
online. In all cases it is because they can't open their log files. I
have to remove the log files before they will start again: in the case
of the samba server I also have to remove quite a few files from the
locks directory. This is a bit of a nuisance..

Surely this is not normal behaviour: certainly, with QNX4 I am used to
being able to perform a shutdown, or even simply hit the reset, and
expect everything to come back OK. This used to be a good selling point
for qnx in fact.

My QNX6.2 box is a stock standard installation. I don't know enough
about QNX6 yet to feel comfortable dicking around with the default
setup! ;-) But is there something I can do to preserve the log files on
shutdown and restart so that the servers can get going?

Thanks,

Geoff Roberts.

Geoff

Re: Corrupted files on system shutdown

Post by Geoff » Tue Dec 03, 2002 12:50 pm

ping.


Geoff wrote:
On my QNX6 box I run a number of standard servers (apache, NTP, Samba).
All of them maintain log files. Both Apache and Samba maintaing lock
files. If I reboot the machine without expressly shutting each one of
these servers down, they won't restart when the machine comes back
online. In all cases it is because they can't open their log files. I
have to remove the log files before they will start again: in the case
of the samba server I also have to remove quite a few files from the
locks directory. This is a bit of a nuisance..

Surely this is not normal behaviour: certainly, with QNX4 I am used to
being able to perform a shutdown, or even simply hit the reset, and
expect everything to come back OK. This used to be a good selling point
for qnx in fact.

My QNX6.2 box is a stock standard installation. I don't know enough
about QNX6 yet to feel comfortable dicking around with the default
setup! ;-) But is there something I can do to preserve the log files on
shutdown and restart so that the servers can get going?

Thanks,

Geoff Roberts.

Mario Charest

Re: Corrupted files on system shutdown

Post by Mario Charest » Wed Dec 04, 2002 12:11 pm

"Geoff" <geoff@rtts.com.au> wrote in message
news:3DECA881.B8A0A9C8@rtts.com.au...
ping.


Geoff wrote:

On my QNX6 box I run a number of standard servers (apache, NTP, Samba).
All of them maintain log files. Both Apache and Samba maintaing lock
files. If I reboot the machine without expressly shutting each one of
these servers down, they won't restart when the machine comes back
online. In all cases it is because they can't open their log files. I
have to remove the log files before they will start again: in the case
of the samba server I also have to remove quite a few files from the
locks directory. This is a bit of a nuisance..

Surely this is not normal behaviour: certainly, with QNX4 I am used to
being able to perform a shutdown, or even simply hit the reset, and
expect everything to come back OK. This used to be a good selling point
for qnx in fact.

My QNX6.2 box is a stock standard installation. I don't know enough
about QNX6 yet to feel comfortable dicking around with the default
setup! ;-) But is there something I can do to preserve the log files on
shutdown and restart so that the servers can get going?
Run chkfsys and that will take care of it.
Thanks,

Geoff Roberts.

Geoff

Re: Corrupted files on system shutdown

Post by Geoff » Wed Dec 04, 2002 1:38 pm

I ran chkfsys -Pqr and yes, it fixed it. Only now when it boots up, it
can't find the rc.sysinit file so it opens up a shell instead (as root).
Fortunately the rc.local file executes and starts up inetd, etc, so I am
able to phindows in.

But I have to say, the requirement to do this in the first place irks me
somewhat, along with a couple of other "features" of QNX6 after having
being spoilt by QNX4.

Geoff.

Mario Charest wrote:
"Geoff" <geoff@rtts.com.au> wrote in message
news:3DECA881.B8A0A9C8@rtts.com.au...
ping.


Geoff wrote:

On my QNX6 box I run a number of standard servers (apache, NTP, Samba).
All of them maintain log files. Both Apache and Samba maintaing lock
files. If I reboot the machine without expressly shutting each one of
these servers down, they won't restart when the machine comes back
online. In all cases it is because they can't open their log files. I
have to remove the log files before they will start again: in the case
of the samba server I also have to remove quite a few files from the
locks directory. This is a bit of a nuisance..

Surely this is not normal behaviour: certainly, with QNX4 I am used to
being able to perform a shutdown, or even simply hit the reset, and
expect everything to come back OK. This used to be a good selling point
for qnx in fact.

My QNX6.2 box is a stock standard installation. I don't know enough
about QNX6 yet to feel comfortable dicking around with the default
setup! ;-) But is there something I can do to preserve the log files on
shutdown and restart so that the servers can get going?


Run chkfsys and that will take care of it.

Thanks,

Geoff Roberts.
--

Realtime Technology Systems Pty Ltd
2 Hadleigh Circuit
Isabella Plains
ACT 2905
AUSTRALIA

Phone: 61-2-6291 3833
Fax: 61-2-6291 3838
Mobile: 0413 634 667
Email: geoff@rtts.com.au

kirk

Re: Corrupted files on system shutdown

Post by kirk » Wed Dec 04, 2002 2:03 pm

This is a known issue, AKA PR10925. It appears this issue should be
repaired with the 6.2.1 product.

Geoff <geoff@rtts.com.au> wrote:
On my QNX6 box I run a number of standard servers (apache, NTP, Samba).
All of them maintain log files. Both Apache and Samba maintaing lock
files. If I reboot the machine without expressly shutting each one of
these servers down, they won't restart when the machine comes back
online. In all cases it is because they can't open their log files. I
have to remove the log files before they will start again: in the case
of the samba server I also have to remove quite a few files from the
locks directory. This is a bit of a nuisance..

Surely this is not normal behaviour: certainly, with QNX4 I am used to
being able to perform a shutdown, or even simply hit the reset, and
expect everything to come back OK. This used to be a good selling point
for qnx in fact.

My QNX6.2 box is a stock standard installation. I don't know enough
about QNX6 yet to feel comfortable dicking around with the default
setup! ;-) But is there something I can do to preserve the log files on
shutdown and restart so that the servers can get going?

Thanks,

Geoff Roberts.
--
Kirk Russell Bridlewood Software Testers Guild

liug

Re: Corrupted files on system shutdown

Post by liug » Wed Dec 04, 2002 4:59 pm

Geoff <geoff@rtts.com.au> wrote:
But I have to say, the requirement to do this in the first place irks me
somewhat, along with a couple of other "features" of QNX6 after having
I have to agree with Geoff. Even if I do a "shutdown" command to shutdown
the qnx6 box, the next boot apache still finds the logs corrupted...
the only way to get around this is to stop the applications and then do
shutdown. if I already stop all applications, why do I still need
"shutdown"? I could just poweroff the box, right?

being spoilt by QNX4.

Geoff.

Mario Charest wrote:

"Geoff" <geoff@rtts.com.au> wrote in message
news:3DECA881.B8A0A9C8@rtts.com.au...
ping.


Geoff wrote:

On my QNX6 box I run a number of standard servers (apache, NTP, Samba).
All of them maintain log files. Both Apache and Samba maintaing lock
files. If I reboot the machine without expressly shutting each one of
these servers down, they won't restart when the machine comes back
online. In all cases it is because they can't open their log files. I
have to remove the log files before they will start again: in the case
of the samba server I also have to remove quite a few files from the
locks directory. This is a bit of a nuisance..

Surely this is not normal behaviour: certainly, with QNX4 I am used to
being able to perform a shutdown, or even simply hit the reset, and
expect everything to come back OK. This used to be a good selling point
for qnx in fact.

My QNX6.2 box is a stock standard installation. I don't know enough
about QNX6 yet to feel comfortable dicking around with the default
setup! ;-) But is there something I can do to preserve the log files on
shutdown and restart so that the servers can get going?


Run chkfsys and that will take care of it.

Thanks,

Geoff Roberts.

--

Realtime Technology Systems Pty Ltd
2 Hadleigh Circuit
Isabella Plains
ACT 2905
AUSTRALIA

Phone: 61-2-6291 3833
Fax: 61-2-6291 3838
Mobile: 0413 634 667
Email: geoff@rtts.com.au

Bill Caroselli (Q-TPS)

Re: Corrupted files on system shutdown

Post by Bill Caroselli (Q-TPS) » Thu Dec 05, 2002 5:31 pm

Hi Geoff

Long time, no hear.

I'm not running 6.2 yet. But I have noticed there are several issues where
QNX6 isn't real graceful about shutting down abruptly. Most that I have
noticed are in Photon programs. If you change a config file and shutdown
Photon and reboot, is screws up the config file. I found that you needed to
shut down Photon and wait for a few seconds or run sync, then you can safely
reboot.

"Geoff" <geoff@rtts.com.au> wrote in message
news:3DEE055D.124AF20E@rtts.com.au...
I ran chkfsys -Pqr and yes, it fixed it. Only now when it boots up, it
can't find the rc.sysinit file so it opens up a shell instead (as root).
Fortunately the rc.local file executes and starts up inetd, etc, so I am
able to phindows in.

But I have to say, the requirement to do this in the first place irks me
somewhat, along with a couple of other "features" of QNX6 after having
being spoilt by QNX4.

Geoff.

Mario Charest wrote:

"Geoff" <geoff@rtts.com.au> wrote in message
news:3DECA881.B8A0A9C8@rtts.com.au...
ping.


Geoff wrote:

On my QNX6 box I run a number of standard servers (apache, NTP,
Samba).
All of them maintain log files. Both Apache and Samba maintaing lock
files. If I reboot the machine without expressly shutting each one
of
these servers down, they won't restart when the machine comes back
online. In all cases it is because they can't open their log files.
I
have to remove the log files before they will start again: in the
case
of the samba server I also have to remove quite a few files from the
locks directory. This is a bit of a nuisance..

Surely this is not normal behaviour: certainly, with QNX4 I am used
to
being able to perform a shutdown, or even simply hit the reset, and
expect everything to come back OK. This used to be a good selling
point
for qnx in fact.

My QNX6.2 box is a stock standard installation. I don't know enough
about QNX6 yet to feel comfortable dicking around with the default
setup! ;-) But is there something I can do to preserve the log files
on
shutdown and restart so that the servers can get going?


Run chkfsys and that will take care of it.

Thanks,

Geoff Roberts.

--

Realtime Technology Systems Pty Ltd
2 Hadleigh Circuit
Isabella Plains
ACT 2905
AUSTRALIA

Phone: 61-2-6291 3833
Fax: 61-2-6291 3838
Mobile: 0413 634 667
Email: geoff@rtts.com.au

Post Reply

Return to “qdn.public.qnxrtp.applications”