Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #79881 > unrolled thread

Shutdown console messages

Back to article view | Back to comp.sys.mac.system

Contents

  Shutdown console messages Neal Reid <NealReid@Nagma.ca> - 2015-09-15 17:57 -0400
    Re: Shutdown console messages Jolly Roger <jollyroger@pobox.com> - 2015-09-16 00:11 +0000
      Re: Shutdown console messages Neal Reid <NealReid@Nagma.ca> - 2015-09-15 20:46 -0400
        Re: Shutdown console messages billy@MIX.COM - 2015-09-16 01:10 +0000
          Re: Shutdown console messages Neal Reid <NealReid@Nagma.ca> - 2015-09-16 00:00 -0400
        Re: Shutdown console messages JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-09-15 21:17 -0400
        Re: Shutdown console messages Jolly Roger <jollyroger@pobox.com> - 2015-09-16 01:29 +0000
          Re: Shutdown console messages Neal Reid <NealReid@Nagma.ca> - 2015-09-15 22:47 -0400
            Re: Shutdown console messages Jolly Roger <jollyroger@pobox.com> - 2015-09-16 14:57 +0000

#79881 — Shutdown console messages

I run with nvram boot-args="-v" so I see boot up and shutdown messages on my 
screen.

Lately, some messages about a stray process and rpc.lockd have flashed past 
during shutdown.

They go by quickly - AND do not show up in the console log!

I don't use amything (that I know of) the uses lockd. I had FUSE for Mac and 
fuse-ext2 installed but took them out. Still flash by shutdown messages...

Doesn't seem to be doing any harm - but I hate not knowing.

Anyone have any idea what might cause:
- stray processes using rpc.lockd might be?
- why messages don't show in the console?
= what I might try to figure this out?
  n

[toc] | [next] | [standalone]

#79882

On 2015-09-15, Neal Reid <NealReid@Nagma.ca> wrote:
> I run with nvram boot-args="-v" so I see boot up and shutdown messages on my 
> screen.

What OS version are you running?

> Lately, some messages about a stray process and rpc.lockd have flashed past 
> during shutdown.

That's nebulous. Verbatim error messages would be much more helpful.

> They go by quickly - AND do not show up in the console log!

Try searching the /var/log/system.log file.

> I don't use amything (that I know of) the uses lockd. I had FUSE for Mac and 
> fuse-ext2 installed but took them out. Still flash by shutdown messages...

rpc.lockd is the NFS file locking daemon.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#79883

In article <d5rqdgFco0dU1@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2015-09-15, Neal Reid <NealReid@Nagma.ca> wrote:
> > I run with nvram boot-args="-v" so I see boot up and shutdown messages on 
> > my 
> > screen.
> 
> What OS version are you running?
Not relevant - but Snow Leopard 
> > Lately, some messages about a stray process and rpc.lockd have flashed past 
> > during shutdown.
> 
> That's nebulous. Verbatim error messages would be much more helpful.
If I could SEE them - I wouldn't be asking how to capture them! 
> > They go by quickly - AND do not show up in the console log!
> 
> Try searching the /var/log/system.log file.
That (and any other) is were they are NOT. That's the point of the question... 
> > I don't use amything (that I know of) the uses lockd. I had FUSE for Mac 
> > and 
> > fuse-ext2 installed but took them out. Still flash by shutdown messages...
> 
> rpc.lockd is the NFS file locking daemon.
Amongst others (e.g. fuse-ext2) - which is why I stated that I didn't use 
amything(sic) that used rpc.lockd.

Thanks anyway

[toc] | [prev] | [next] | [standalone]

#79885

Neal Reid <NealReid@nagma.ca> writes, quoting
Jolly Roger <jollyroger@pobox.com>:

> > That's nebulous. Verbatim error messages would be much more helpful.
> If I could SEE them - I wouldn't be asking how to capture them! 

They could be written to dmesg, but then that gets blown away on
the next boot.

> > Try searching the /var/log/system.log file.
> That (and any other) is were they are NOT. That's the point of the question... 

To enable logging, you'll need to edit this file...

/System/Library/LaunchDaemons/com.apple.lockd.plist

...and add the -d option as shown here -

        <key>ProgramArguments</key>
        <array>
                <string>/usr/sbin/rpc.lockd -d 1</string>
        </array>

Debugging level one is probably adequate, but if not, try two.

Billy Y..
-- 
        sub     #'9+1   ,r0             ; convert ascii byte
	add     #9.+1   ,r0             ; to an integer
	bcc     20$                     ; not a number

[toc] | [prev] | [next] | [standalone]

#79889

In article <mtafhg$o2v$1@reader2.panix.com>, billy@MIX.COM wrote:
> To enable logging, you'll need to edit this file...
> 
> /System/Library/LaunchDaemons/com.apple.lockd.plist
> 
> ...and add the -d option as shown here -
> 
>         <key>ProgramArguments</key>
>         <array>
>                 <string>/usr/sbin/rpc.lockd -d 1</string>
>         </array>
> 
> Debugging level one is probably adequate, but if not, try two.
Helped - oddly. The following showed up:
/sbin/nfsd[86]: Lockd did not start!
/sbin/nfsd[86]: can't register NFS/UDP service.
/sbin/nfsd[86]: can't register NFS/TCP service.
/sbin/nfsd[86]: can't register MOUNT/UDP service.
/sbin/nfsd[86]: can't register MOUNT/TCP service.
/sbin/nfsd[86]: DNSServiceRegister(_nfs._tcp) failed with -65563
/sbin/nfsd[86]: Can't get lockd mach port!

Now, how enabling debug in rpc.lockd exposed nfs problems...

I strongly suspect the DNS bit may be central, but I can't prove it.

I've poked around restarting various nfs / rpc deamons with no luck.

Ideas?

[toc] | [prev] | [next] | [standalone]

#79886

On 15-09-15 20:46, Neal Reid wrote:

> If I could SEE them - I wouldn't be asking how to capture them! 

Cue the fancy iPhone with a movie camera. Yes, you film the screen as
you /boot/shutdown.  Once booted back, you transfertro itunes and can
use quicktime to vew frame by frame which gives you ability to look at
each message.

For early boot, a lot goes on before launchd starts and I am not sure it
gets logged anywhere.

In the good old days, we had serial ports for those messages and they
first got printed on printers, and later onto consome management
software that logged data from serial port (and detected certain strings
to launch alarms).

Apple no longer supports booting from serial port.

[toc] | [prev] | [next] | [standalone]

#79887

On 2015-09-16, Neal Reid <NealReid@Nagma.ca> wrote:
> In article <d5rqdgFco0dU1@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:
>> On 2015-09-15, Neal Reid <NealReid@Nagma.ca> wrote:
>>> I run with nvram boot-args="-v" so I see boot up and shutdown
>>> messages on my screen.
>> 
>> What OS version are you running?
>
> Not relevant - but Snow Leopard 

It might actually be relevant, which is why I asked.

>>> Lately, some messages about a stray process and rpc.lockd have
>>> flashed past during shutdown.
>> 
>> That's nebulous. Verbatim error messages would be much more helpful.
>
> If I could SEE them - I wouldn't be asking how to capture them! 

Calm down. : ) I suppose you could try taking a picture of them and then
transcribing the verbatim message that way.

>> > They go by quickly - AND do not show up in the console log!
>> 
>> Try searching the /var/log/system.log file.
>
> That (and any other) is were they are NOT.

You hadn't mentioned the system log; so I figured I would make sure you
actually looked at it.

>>> I don't use amything (that I know of) the uses lockd. I had FUSE for
>>> Mac and fuse-ext2 installed but took them out. Still flash by
>>> shutdown messages...
>> 
>> rpc.lockd is the NFS file locking daemon.
>
> Amongst others (e.g. fuse-ext2) - which is why I stated that I didn't use 
> amything(sic) that used rpc.lockd.

You said you had fuse installed at one point. How sure are you that you
removed it *completely*? What method did you use to remove it?

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#79888

In article <d5rv0dFdni3U1@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2015-09-16, Neal Reid <NealReid@Nagma.ca> wrote:
> > In article <d5rqdgFco0dU1@mid.individual.net>,
> >  Jolly Roger <jollyroger@pobox.com> wrote:
> >> What OS version are you running?
> > Not relevant - but Snow Leopard  
> It might actually be relevant, which is why I asked.
True - I'm just tired of being ragged on because I support old systems. I was 
trying to avoid hassle - but you're correct - it could have been relevant.
> Calm down. : ) I suppose you could try taking a picture of them and then
> transcribing the verbatim message that way.
Sorry. Hard to get tone correct in writing. A picture would be hard. I'll give a 
shot at a video...

> You hadn't mentioned the system log; so I figured I would make sure you
> actually looked at it.
Again, me trying to keep it short. I've watched everything logged to console DB. 
As an aside, s anything NOT logged to "All messages" ? 

> You said you had fuse installed at one point. How sure are you that you
> removed it *completely*? What method did you use to remove it?
The code for the whole FUSE for OSX suite is available. I read it and removed 
everything.

One of my habits is to do a clean install of whatever, touch a file,  then look 
at everything modified after the touch and remove as needed. 

Sorry for the tone - I've been working with Macs since before they were Macs (my 
1st was a Lisa). I have a hard time expressing myself neither as a noobie or a 
wizard...

About to try with the debug hack mentioned down thread...

[toc] | [prev] | [next] | [standalone]

#79891

On 2015-09-16, Neal Reid <NealReid@Nagma.ca> wrote:
> In article <d5rv0dFdni3U1@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:
>> On 2015-09-16, Neal Reid <NealReid@Nagma.ca> wrote:
>>> In article <d5rqdgFco0dU1@mid.individual.net>,
>>>  Jolly Roger <jollyroger@pobox.com> wrote:
>>>
>>>> What OS version are you running?
>>>
>>> Not relevant - but Snow Leopard  
>>
>> It might actually be relevant, which is why I asked.
>
> True - I'm just tired of being ragged on because I support old systems. I was 
> trying to avoid hassle - but you're correct - it could have been relevant.
>
>> Calm down. : ) I suppose you could try taking a picture of them and then
>> transcribing the verbatim message that way.
>
> Sorry. Hard to get tone correct in writing. A picture would be hard. I'll give a 
> shot at a video...
>
>> You hadn't mentioned the system log; so I figured I would make sure you
>> actually looked at it.
>
> Again, me trying to keep it short. I've watched everything logged to console DB. 
> As an aside, s anything NOT logged to "All messages" ? 

Some startup messages that happen before logging facilities are up and
running aren't included, and perhaps some at shutdown. Usually, those
aren't what you are looking for, though, since they are very low-level.

>> You said you had fuse installed at one point. How sure are you that you
>> removed it *completely*? What method did you use to remove it?
>
> The code for the whole FUSE for OSX suite is available. I read it and removed 
> everything.
>
> One of my habits is to do a clean install of whatever, touch a file,  then look 
> at everything modified after the touch and remove as needed. 

Did you remove the files manually, or did you use an official
uninstaller? What steps did you take, specifically? 

I'm wondering if something wasn't left over.

> Sorry for the tone - I've been working with Macs since before they were Macs (my 
> 1st was a Lisa). I have a hard time expressing myself neither as a noobie or a 
> wizard...

I've got a Lisa with Macintosh XL upgrade and ProFile drive sitting in
my closet here. You're not alone. ; )

> About to try with the debug hack mentioned down thread...

Good luck! *fingers crossed*

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.mac.system

csiph-web