I've never seen these before, so I have no idea what they are to even figure it out. I do know that I never had them when running KDE 2.1 but now with KDE 2.2 they're there. Aug 24 21:58:25 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 Aug 24 21:58:25 daydream kernel: lockd: cannot monitor 192.168.0.11 Aug 24 21:58:25 daydream kernel: lockd: failed to monitor 192.168.0.11 Aug 24 21:58:28 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 Aug 24 21:58:28 daydream kernel: lockd: cannot monitor 192.168.0.11 Aug 24 21:58:28 daydream kernel: lockd: failed to monitor 192.168.0.11 Aug 24 21:58:32 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 Aug 24 21:58:32 daydream kernel: lockd: cannot monitor 192.168.0.11 Aug 24 21:58:32 daydream kernel: lockd: failed to monitor 192.168.0.11 Anyone know what these are? If not, I can start digging/playing till I find it, but I'm hopeing someone will know it right off. -- S.Toms - smotrs@mindspring.com - www.mindspring.com/~smotrs SuSE Linux v7.0+ - Kernel 2.2.18 Is it possible that software is not like anything else, that it is meant to be discarded: that the whole point is to always see it as a soap bubble?
* S.Toms (smotrs@mindspring.com) [010824 22:07]: -> I've never seen these before, so I have no idea what they are to even ->figure it out. I do know that I never had them when running KDE 2.1 but ->now with KDE 2.2 they're there. -> ->Aug 24 21:58:25 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 ->Aug 24 21:58:25 daydream kernel: lockd: cannot monitor 192.168.0.11 ->Aug 24 21:58:25 daydream kernel: lockd: failed to monitor 192.168.0.11 ->Aug 24 21:58:28 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 ->Aug 24 21:58:28 daydream kernel: lockd: cannot monitor 192.168.0.11 ->Aug 24 21:58:28 daydream kernel: lockd: failed to monitor 192.168.0.11 ->Aug 24 21:58:32 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 ->Aug 24 21:58:32 daydream kernel: lockd: cannot monitor 192.168.0.11 ->Aug 24 21:58:32 daydream kernel: lockd: failed to monitor 192.168.0.11 -> -> Anyone know what these are? If not, I can start digging/playing till I ->find it, but I'm hopeing someone will know it right off. they are related to NFS..Do you have NFS mounts too or from the two machines in question? -- Ben Rosenberg mailto:ben@whack.org cat CE|ME|NT|XP > /dev/null
On Fri, 24 Aug 2001, Ben Rosenberg wrote: br> * S.Toms (smotrs@mindspring.com) [010824 22:07]: br> -> I've never seen these before, so I have no idea what they are to even br> ->figure it out. I do know that I never had them when running KDE 2.1 but br> ->now with KDE 2.2 they're there. br> -> br> ->Aug 24 21:58:25 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 br> ->Aug 24 21:58:25 daydream kernel: lockd: cannot monitor 192.168.0.11 br> ->Aug 24 21:58:25 daydream kernel: lockd: failed to monitor 192.168.0.11 br> ->Aug 24 21:58:28 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 br> ->Aug 24 21:58:28 daydream kernel: lockd: cannot monitor 192.168.0.11 br> ->Aug 24 21:58:28 daydream kernel: lockd: failed to monitor 192.168.0.11 br> ->Aug 24 21:58:32 daydream kernel: nsm_mon_unmon: rpc failed, status=-93 br> ->Aug 24 21:58:32 daydream kernel: lockd: cannot monitor 192.168.0.11 br> ->Aug 24 21:58:32 daydream kernel: lockd: failed to monitor 192.168.0.11 br> -> br> -> Anyone know what these are? If not, I can start digging/playing till I br> ->find it, but I'm hopeing someone will know it right off. br> br> they are related to NFS..Do you have NFS mounts too or from the two br> machines in question? br> Yeah, as a matter of fact, I have three mounts from that computer, all done with autofs. One is for the home paths, another for all my music and the third is where I keep all files/documents/rpm's (src and bin). But I've been using 7.0 now and had it configured this way since 7.0 was released and havn't ever seen these before. The only thing I've changed was an upgrade to KDE, then about the next day I started getting logfiles full of those errors. :/ br> -- S.Toms - smotrs@mindspring.com - www.mindspring.com/~smotrs SuSE Linux v7.0+ - Kernel 2.2.18 Alden's Laws: (1) Giving away baby clothes and furniture is the major cause of pregnancy. (2) Always be backlit. (3) Sit down whenever possible.
-> -> Yeah, as a matter of fact, I have three mounts from that computer, all ->done with autofs. One is for the home paths, another for all my music and ->the third is where I keep all files/documents/rpm's (src and bin). -> But I've been using 7.0 now and had it configured this way since 7.0 was ->released and havn't ever seen these before. The only thing I've changed ->was an upgrade to KDE, then about the next day I started getting logfiles ->full of those errors. :/ -> Well, I haven't used KDE in an environment which required NFS since 2.1 so I'm not sure how 2.2 could screw up NFS .. I doubt it could. But I would take a look for "lisa" which is this goofy network service that appeared with 2.2 Final. I disabled it until I could read more about it. It's about as annoying as that Medusa service that Gnome uses. I've disabled both...I'm mean how many of these background services do we need. *grin* Check that out and see if that solves your issue. -- Ben Rosenberg mailto:ben@whack.org cat CE|ME|NT|XP > /dev/null
On Fri, 24 Aug 2001, Ben Rosenberg wrote: br> -> br> -> Yeah, as a matter of fact, I have three mounts from that computer, all br> ->done with autofs. One is for the home paths, another for all my music and br> ->the third is where I keep all files/documents/rpm's (src and bin). br> -> But I've been using 7.0 now and had it configured this way since 7.0 was br> ->released and havn't ever seen these before. The only thing I've changed br> ->was an upgrade to KDE, then about the next day I started getting logfiles br> ->full of those errors. :/ br> -> br> br> Well, I haven't used KDE in an environment which required NFS since 2.1 br> so I'm not sure how 2.2 could screw up NFS .. I doubt it could. But I br> would take a look for "lisa" which is this goofy network service that br> appeared with 2.2 Final. I disabled it until I could read more about it. br> It's about as annoying as that Medusa service that Gnome uses. I've br> disabled both...I'm mean how many of these background services do we br> need. *grin* br> Ben, How exactly did you disable it? I assumed it was the following: Control Center> Network> LAN Browsing followed by checking 'Never' on all four items under the tab lan:/ and rlan:/ configuration but even doing this as root and as user and even restarting doesn't seem to disable it, or stop the previous messages. Maybe it is being disabled but the messages are something else. br> Check that out and see if that solves your issue. br> br> -- S.Toms - smotrs@mindspring.com - www.mindspring.com/~smotrs SuSE Linux v7.0+ - Kernel 2.2.18 Pick another fortune cookie.
* S.Toms (smotrs@mindspring.com) [010825 22:07]: -> How exactly did you disable it? I assumed it was the following: -> Control Center> Network> LAN Browsing -> ->followed by checking 'Never' on all four items under the tab -> lan:/ and rlan:/ configuration -> ->but even doing this as root and as user and even restarting doesn't seem ->to disable it, or stop the previous messages. Maybe it is being disabled ->but the messages are something else. -> -> I went into /etc/rc.d/rc3.d and moved S12lisa to off.S12lisa..then just ./off.S12lisa stop ... and it was taken care of. It hasn't run since. :) -- Ben Rosenberg mailto:ben@whack.org cat CE|ME|NT|XP > /dev/null
On Sat, 25 Aug 2001, Ben Rosenberg wrote: br> * S.Toms (smotrs@mindspring.com) [010825 22:07]: br> br> ->but even doing this as root and as user and even restarting doesn't seem br> ->to disable it, or stop the previous messages. Maybe it is being disabled br> ->but the messages are something else. br> -> br> -> br> br> br> I went into /etc/rc.d/rc3.d and moved S12lisa to off.S12lisa..then just br> ./off.S12lisa stop ... and it was taken care of. It hasn't run since. :) br> Ok, I don't think it's lisa then, I don't have any init files that contain lisa in it's name or resembles what you suggested above. br> -- S.Toms - smotrs@mindspring.com - www.mindspring.com/~smotrs SuSE Linux v7.0+ - Kernel 2.2.18 The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian Proverb
On Sat, 25 Aug 2001, S.Toms wrote: st> On Sat, 25 Aug 2001, Ben Rosenberg wrote: st> st> br> * S.Toms (smotrs@mindspring.com) [010825 22:07]: st> br> st> br> ->but even doing this as root and as user and even restarting doesn't seem st> br> ->to disable it, or stop the previous messages. Maybe it is being disabled st> br> ->but the messages are something else. st> br> -> st> br> -> st> br> st> br> st> br> I went into /etc/rc.d/rc3.d and moved S12lisa to off.S12lisa..then just st> br> ./off.S12lisa stop ... and it was taken care of. It hasn't run since. :) st> br> st> st> Ok, I don't think it's lisa then, I don't have any init files that st> contain lisa in it's name or resembles what you suggested above. st> Ben, Just thought I'd keep ya informed. It's definately somehting within the 2.2.2 upgrades. I've dumped and reinstalled from scratch, back to 2.1.2 and now the messages described previously no longer exist. The packages used in each install are as follows KDE - 2.1.2 KDE - 2.2.2 audiofile-0.2.1-11.rpm -- Removed -- kdeadmin-2.1.1-8.rpm kdeadmin-2.2.0-1.i386.rpm kdebase-2.1.1-6.rpm kdebase-2.2.0-0.i386.rpm kdebase-devel-2.1.1-6.rpm kdebase-devel-2.2.0-0.i386.rpm kdegames-2.1.1-7.rpm kdegames-2.2.0-1.i386.rpm kdegraphics-2.1.1-7.rpm kdegraphics-2.2.0-1.i386.rpm kdelibs-2.1.2-0.rpm kdelibs-2.2.0-1.i386.rpm kdelibs-devel-2.1.2-0.rpm kdelibs-devel-2.2.0-1.i386.rpm kdemultimedia-2.1.1-7.rpm kdemultimedia-2.2.0-1.i386.rpm kdenetwork-2.1.1-5.rpm kdenetwork-2.2.0-1.i386.rpm kdepim-2.1.1-8.rpm kdepim-2.2.0-1.i386.rpm kdesupport-2.1.1-3.rpm -- Removed -- kdesupport-devel-2.1.1-3.rpm -- Removed -- kdetoys-2.1.1-8.rpm kdetoys-2.2.0-1.i386.rpm kdeutils-2.1.1-7.rpm kdeutils-2.2.0-0.i386.rpm liblcms-1.06-37.rpm -- Removed -- libmng-0.9.3-9.rpm -- Removed -- qt-2.3.0-13.rpm qt-2.3.1-25.i386.rpm qt-devel-2.3.0-13.rpm qt-devel-2.3.1-25.i386.rpm but something in 2.2.2 is causing issues. Havn't narrowed it down any further, but now I'm gonna try it with just a base install of KDE-2.2.2 and see what happens from there. st> br> st> st> -- S.Toms - smotrs@mindspring.com - www.mindspring.com/~smotrs SuSE Linux v7.0+ - Kernel 2.2.18 "I cannot and will not cut my conscience to fit this year's fashions." -- Lillian Hellman
participants (2)
-
Ben Rosenberg -
S.Toms