log of boot process

I'm running kubutu, a derivative of debian and NFS is not starting
up for me. During the boot process, I'm pretty sure I see an error
message, but it scrolls by too fast to read.

I've looked at syslog.conf and seen that most of my log files
are in /var/log. When I look for NFS errors, I cannot find any.
Is there a standard location for the log created when the PC
reboots?

Thanks for any help in advance.

Jim Anderson

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim Anderson wrote:
>
> I'm running kubutu, a derivative of debian and NFS is not starting
> up for me. During the boot process, I'm pretty sure I see an error
> message, but it scrolls by too fast to read.
>
> I've looked at syslog.conf and seen that most of my log files
> are in /var/log. When I look for NFS errors, I cannot find any.
> Is there a standard location for the log created when the PC
> reboots?
>
> Thanks for any help in advance.

dmesg | more

The dmesg messages should also be captured in one of the logs in /var/log


- --

Lew Pitcher, IT Specialist, Corporate Technology Solutions,
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEfdjkagVFX4UWr64RAomgAKDSnvoOun6RfxrWxU3QtZ 931Uye3QCgmACh
fWlAB3TSZ8Fcz7tgMfCJ7j0=
=mzKl
-----END PGP SIGNATURE-----

Lew,

Thank you for the help. That clears up at least part of the
picture, but I'm not sure all of it. I checked and there
is a file /var/log/dmesg. The reason I did not see it was
that in my search, I grepped for 'nfs|NFS' and no nfs messages
not appear in the file.

There must be more to the picture, because I know there
are some nfs messages that scroll by during the boot process.

Once this is message sent, I'm going to reboot one or more times
to see if I can confirm seeing nfs messages that are not
showing up with dmesg.

Jim

Lew Pitcher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jim Anderson wrote:
>
>>I'm running kubutu, a derivative of debian and NFS is not starting
>>up for me. During the boot process, I'm pretty sure I see an error
>>message, but it scrolls by too fast to read.
>>
>>I've looked at syslog.conf and seen that most of my log files
>>are in /var/log. When I look for NFS errors, I cannot find any.
>>Is there a standard location for the log created when the PC
>>reboots?
>>
>>Thanks for any help in advance.
>
>
> dmesg | more
>
> The dmesg messages should also be captured in one of the logs in /var/log
>
>
> - --
>
> Lew Pitcher, IT Specialist, Corporate Technology Solutions,
> Enterprise Technology Solutions, TD Bank Financial Group
>
> (Opinions expressed here are my own, not my employer's)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFEfdjkagVFX4UWr64RAomgAKDSnvoOun6RfxrWxU3QtZ 931Uye3QCgmACh
> fWlAB3TSZ8Fcz7tgMfCJ7j0=
> =mzKl
> -----END PGP SIGNATURE-----

As I suspected there was an NFS error message that something
about NFS not starting because there were no files to export.

I add my export file and then lots of NFS messages showed up
in dmesg. I consider it a bug that the error message fails
to show up in the log.

Jim

Lew Pitcher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jim Anderson wrote:
>
>>I'm running kubutu, a derivative of debian and NFS is not starting
>>up for me. During the boot process, I'm pretty sure I see an error
>>message, but it scrolls by too fast to read.
>>
>>I've looked at syslog.conf and seen that most of my log files
>>are in /var/log. When I look for NFS errors, I cannot find any.
>>Is there a standard location for the log created when the PC
>>reboots?
>>
>>Thanks for any help in advance.
>
>
> dmesg | more
>
> The dmesg messages should also be captured in one of the logs in /var/log
>
>
> - --
>
> Lew Pitcher, IT Specialist, Corporate Technology Solutions,
> Enterprise Technology Solutions, TD Bank Financial Group
>
> (Opinions expressed here are my own, not my employer's)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFEfdjkagVFX4UWr64RAomgAKDSnvoOun6RfxrWxU3QtZ 931Uye3QCgmACh
> fWlAB3TSZ8Fcz7tgMfCJ7j0=
> =mzKl
> -----END PGP SIGNATURE-----

Jim Anderson <ezjab@ieee.org> wrote:
>
> Lew,
>
> Thank you for the help. That clears up at least part of the
> picture, but I'm not sure all of it. I checked and there
> is a file /var/log/dmesg. The reason I did not see it was
> that in my search, I grepped for 'nfs|NFS' and no nfs messages
> not appear in the file.
>
> There must be more to the picture, because I know there
> are some nfs messages that scroll by during the boot process.
>
> Once this is message sent, I'm going to reboot one or more times
> to see if I can confirm seeing nfs messages that are not
> showing up with dmesg.
>
> Jim

AFAIK dmesg is for kernel messages, your errors are in a startup
script so they aren't getting logged anywhere because syslogd has not
yet started.

Find where in the startup scripts NFS is started and put the command
read junk
in there to stop the startup script so you can read the message, or
try invoking the startup script for NFS manually, if you're lucky
you'll get the same error.

Jerry
---snip--

On Wed, 31 May 2006, in the Usenet newsgroup comp.os.linux.admin, in article
<0lnfg.120$Cw3.14@trndny01>, Jim Anderson wrote:

[Please do not post the same article in multiple news groups. If you feel
you absolutely _must_ do so, include all newsgroup name as a comma separated
list in the newsgroup header, AND SET A "Followup-To:" header.]

>I add my export file and then lots of NFS messages showed up
>in dmesg. I consider it a bug that the error message fails
>to show up in the log.

Error messages are sent to stderr, which during the boot process is the
console. You are apparently using some GUI login manager, which prevents
you from scrolling back through the frame buffer (using the left shift and
page-up keys together) BEFORE login, or starting a display manager.

Remember that during a boot (at least during the early stages) there is no
writable file system to write to.

Old guy