Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

unix

    Next

  • 1. v20z and SP - bad console connection?
    Hi, I'm having a bit of difficulty 'consoling' (as in "platform console") from SP. It seems like the system comes up fine (i.e. BIOS setup is ok) until the OS loads up (from HD), a point at which it just goes blank or/and becomes unresponsive. I've tried to boot off of the installation CDs (e.g. Suse Pro 9.2, Sol 10) without success - for instance, with the Sol 10, the installation menu would come and wait for my input, then it freezes; Suse Prof 9.2 doesn't fare well either - the lilo text would come up for a couple of seconds, then it goes straight to "the secondary OS boot.. yayaya". Any idea what went wrong? I'm using the default configuration at bios level - that is, other than the baud rate (which I changed from 9600 to 38400 to again 9600) everything is set to default value. shm
  • 2. /var size?
    hello, reading install docs, i notice: If you intend to use the crash dump feature savecore(1M), allocate double the amount of your physical memory in the /var file system. v440 has 16Go RAM. Do i intend to fix 32 Go for /var? is it necessary? thanks, gerard
  • 3. md5 Checksum
    Hi All, I downloaded solaris 10, and I have three issues. The DVD image consists of 5 segements. issue 1. when I did unzip on the iso, I got some verbage in French. I don't know what it says. Did I download the wrong version? The link said that I was downloading a multilanguage version. I hope English is included? issue 2: the instructions ask to check the md5 checksum using "mdsum check" Where can I obtain mdsum from? It is not on my Solaris 9 system. issue 3: can I install Solaris 10 while keeping all my user files intact? Will the install wipe out everything or will I be able to save the user files? Thanks for your help, JS
  • 4. hardware needed for solaris 10
    I would like to know if the following system could be enought for running Solaris 10 ? The typical use will be as learning system for sysadmin and network test but without heavy processes. SUN Sparc Ultra 5 Workstation 360 Mhz 256 MB RAM, 8.22 GB hard disk drive, CD drive, floppy disk drive, 10/100Base-Tx Ethernet thanks in advance, best regards.

Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby gazelle » Thu, 23 Oct 2003 01:23:38 GMT

Solaris: Shutting down one system generates messages on all
systems: Why/how to turn off?

When one machine in our network executes the shutdown command, messages are
displayed on all the machines saying the machine is about to be rebooted
(which is not true on those other machines).  I'm guessing that this is
caused by the fact that the other machines have NFS-mounted drives on the
machine that is going down.

Is this right?  And, is there a way to turn this "feature" off?

Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby Darren Dunham » Thu, 23 Oct 2003 01:55:18 GMT





Take a look at the man page for 'rmtab'.

-- 
Darren Dunham                                            XXXX@XXXXX.COM 
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby gazelle » Thu, 23 Oct 2003 04:06:15 GMT

In article <Wxdlb.1628$ XXXX@XXXXX.COM >,





OK, and then?

I get the idea of the rmtab file, but there doesn't seem to be much you can
do with it.  And, I don't see how it relates to the instant problem - unless
what you are saying is that removing (or commenting out) lines in this file
will inhibit the sending of the inter-system broadcast message.

Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby Barry Margolin » Thu, 23 Oct 2003 04:19:57 GMT

In article <bn40f0$6c9$ XXXX@XXXXX.COM >,






Yes it will.  That's how the NFS server knows which clients have mounted
its filesystems, and therefore need to be warned about the impending
shutdown.

-- 
Barry Margolin,  XXXX@XXXXX.COM 
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.

Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby Oscar del Rio » Thu, 23 Oct 2003 04:37:28 GMT



Disable walld in /etc/inetd.conf on all the machines, or
edit /usr/sbin/shutdown (a shell script) and comment out
the "rwall" line.


Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby Darren Dunham » Thu, 23 Oct 2003 04:49:04 GMT






Well, that's the background for what's happening.  I don't know exactly
what part of shutdown reads that file to send out messages, so I'm not
certain how it can be bypassed.


You can certainly do that.  If I were very {*filter*}about it, I might save a
copy and and put it back before starting up mountd on the reboot.  If
you don't do that, I can't think of anything that would break, though.
The output of 'showmount' would be inaccurate of course.

-- 
Darren Dunham                                            XXXX@XXXXX.COM 
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby gazelle » Thu, 23 Oct 2003 04:57:26 GMT

In article <xFflb.144$ XXXX@XXXXX.COM >,


...

OK - this sounds like a workable workaround.  I can hack together a script
to comment out all the rmtab entries and add that to the shutdown script.

But, for the sake of clarity, is there not a more direct/cleaner solution?

P.S.  I can see the logic behind this feature, but in a production
environment (with clerical level users), it is an annoyance.

Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby Logan Shaw » Thu, 23 Oct 2003 05:04:14 GMT






Or just run "init 6" instead of "shutdown -i6", etc.  "init 6"
is pretty much the same thing as "shutdown -i6 -g0 -y", except
for the notifications and the fact that it creates /etc/nologin.
(But the window of time that /etc/nologin exists is short.)

   - Logan


Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby gazelle » Thu, 23 Oct 2003 05:06:33 GMT

In article < XXXX@XXXXX.COM >,





Bingo!  I have to admit it never occurred to me that "shutdown" would be
implemented as a shell script.

It looks like all you have to do is comment out this one single line:

	remotes=`/usr/sbin/showmount`


Re: Solaris: Shutting down one system generates messages on all systems: Why/how to turn off?

Postby Darren Dunham » Thu, 23 Oct 2003 05:06:33 GMT






Heh.. That explains it.  I was looking through all the shutdown
processes and not at shutdown itself.

-- 
Darren Dunham                                            XXXX@XXXXX.COM 
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Similar Threads:

1.windows server shutting down linux systems

I have windows server 2003 installed in  my lab.
I want this to shut down linux clinets remotely at  a specified time
automatically daily.
How can i do that

2.cornflicker shuts down French weapons system ..

3.System won't shut down...

Hello, I've got a server (kernel 2.6.9) that is in trouble. An external 
USB disk has throw an error. In order to get it into a good state I 
would like to reboot it, but it won't let me.

What I was doiung was untaring a file on an external USB disk. This tar 
at one moment just hung there, not doing anything.

dmesg shows lots of errors like

SCSI error : <1 0 0 0> return code = 0x6000000
end_request: I/O error, dev sda, sector 3150391

En then the following:

scsi: Device offlined - not ready after error recovery: host 1 channel 0 
id 0 lun 0
sd 1:0:0:0: Illegal state transition cancel->offline
Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1688
  [<c0346346>] scsi_device_set_state+0x96/0xe0
  [<c0344340>] scsi_eh_offline_sdevs+0x50/0x70
  [<c0344741>] scsi_unjam_host+0xc1/0xd0
  [<c03447ed>] scsi_error_handler+0x9d/0xc0
  [<c0344750>] scsi_error_handler+0x0/0xc0
  [<c0104295>] kernel_thread_helper+0x5/0x10
SCSI error : <1 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 3150439
------------[ cut here ]------------
kernel BUG at drivers/block/as-iosched.c:1852!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in: vt1211 i2c_sensor i2c_isa ipt_TOS iptable_mangle 
ipt_MASQUERADE iptable_nat ipt_REJECT ipt_ULOG ipt_state ip_conntrack 
ipt_LOG iptable_filter ip_tables via_rhine mii usb_storage ehci_hcd usbcore
CPU:    0
EIP:    0060:[<c031318f>]    Not tainted VLI
EFLAGS: 00010297   (2.6.9-gentoo-r1)
EIP is at as_exit+0x5f/0x70
eax: c6b02ed4   ebx: c6b02ec0   ecx: 00000000   edx: c8fc1e98
esi: c12af834   edi: 00000282   ebp: cdceceb4   esp: c8fc1ed8
ds: 007b   es: 007b   ss: 0068
Process scsi_eh_1 (pid: 23983, threadinfo=c8fc0000 task=cd59eaa0)
Stack: c12af7a8 c030a584 c12af7a8 c12af7b4 c030c4d6 c12af7a8 c1d03024 
c1d03000
        c0347c66 c12af7a8 c1d031a8 c047d2f0 c047d320 cdceced8 c03066a4 
c1d03184
        c02a96c7 c1d031a8 c1d031c0 c02a96d0 c1d03000 00000000 c02a99e5 
c1d031a8
Call Trace:
  [<c030a584>] elevator_exit+0x14/0x20
  [<c030c4d6>] blk_cleanup_queue+0x26/0x70
  [<c0347c66>] scsi_device_dev_release+0xf6/0x110
  [<c03066a4>] device_release+0x14/0x50
  [<c02a96c7>] kobject_cleanup+0x67/0x70
  [<c02a96d0>] kobject_release+0x0/0x10
  [<c02a99e5>] kref_put+0x25/0x70
  [<c02a96f6>] kobject_put+0x16/0x20
  [<c02a96d0>] kobject_release+0x0/0x10
  [<c0341a12>] __scsi_iterate_devices+0x72/0x90
  [<c0343e8b>] scsi_eh_stu+0x8b/0xf0
  [<c03445b7>] scsi_eh_ready_devs+0x17/0x60
  [<c0344741>] scsi_unjam_host+0xc1/0xd0
  [<c03447ed>] scsi_error_handler+0x9d/0xc0
  [<c0344750>] scsi_error_handler+0x0/0xc0
  [<c0104295>] kernel_thread_helper+0x5/0x10
Code: 83 d8 00 00 00 50 e8 11 b2 ff ff 8b 43 38 50 e8 d8 ee e2 ff 83 c4 
0c 89 5c 24 08 5b e9 cb ee e2 ff 0f 0b 3d 07 b2 bd 3f c0 eb cb <0f> 0b 
3c 07 b2 bd 3f c0 eb b9 8d b4 26 00 00 00 00 55 57 56 53


Now the situation is that processes that where using the affected 
filesystem are hanging, and resist any atempt to be shut down.
(They ignore a kill -9)

The rest of the system is unaffected. But as I want to get the system in 
a good state again I want to reboot.

But it won't.

shutdown -h now, or even a "reboot" only results in a message on the 
terminals, and the process adding itself to the list of hanging 
processes that refuce to be killed.
I tried init 0 but that was ignored.

I'm about to powercycle this system, but is there anything else one can 
do in such a situation?

The weird thing is that the system is otherwise unafected. Ok. the 
external USB disk is not there. I've got a hanging tar, a hanging bash, 
a hanging ls that all refuse to go away when kill -9 -ed. I have also a 
hanging reboot, a hanging shutdown. Init is ignored. But the mail and 
www server are OK, and I can still log in using ssh...

What to do now?

Krist

4.System Shuts Down after successful resume from suspend to ram

I've got a Tecra M1. I was running SuSE 9.1 with a hand-built 2.6.11.3
kernel and the latest NVidia drivers. In that config both suspend to
ram and suspend to disk both worked fine.

I've now rebuilt the box and installed SuSE 9.3. The (stock) kernel is
2.6.11.4-20a-default. I am also now running gdm (something I've never
done before.) Suspend to disk works just fine. Suspend to ram also
works fine, but about 20 seconds after resuming, the system starts a
shutdown. The kernel reports  "Received signal 15, shutting down
cleanly". This is somehow related to gconfd.

What I see in my /var/log/messages follows a bit further below.

I am looking for advice on having the system not shutdown this way.

Thanks
John

Apr 24 08:40:49 linux kernel: Stopping tasks:
====================================================================================================|
Apr 24 08:40:49 linux kernel: eth1: Going into suspend...
Apr 24 08:40:49 linux kernel: NVRM: RmPowerManagement: 3
Apr 24 08:40:49 linux kernel: Back to C!
Apr 24 08:40:49 linux kernel: Warning: CPU frequency is 1600000,
cpufreq assumed 600000 kHz.
Apr 24 08:40:49 linux kernel: PCI: Setting latency timer of device
0000:00:1d.0 to 64
Apr 24 08:40:49 linux kernel: PCI: Setting latency timer of device
0000:00:1d.1 to 64
Apr 24 08:40:49 linux kernel: PCI: Setting latency timer of device
0000:00:1d.2 to 64
Apr 24 08:40:49 linux kernel: PCI: cache line size of 32 is not
supported by device 0000:00:1d.7
Apr 24 08:40:49 linux kernel: ehci_hcd 0000:00:1d.7: USB 2.0 restarted,
EHCI 1.00, driver 10 Dec 2004
Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:00:1f.1[A] ->
GSI 11 (level, low) -> IRQ 11
Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:00:1f.5[B] ->
GSI 11 (level, low) -> IRQ 11
Apr 24 08:40:49 linux kernel: PCI: Setting latency timer of device
0000:00:1f.5 to 64
Apr 24 08:40:49 linux kernel: NVRM: RmPowerManagement: 4
Apr 24 08:40:49 linux kernel: eth1: Coming out of suspend...
Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:02:05.0[A] ->
GSI 11 (level, low) -> IRQ 11
Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:02:07.0[A] ->
GSI 11 (level, low) -> IRQ 11
Apr 24 08:40:49 linux kernel: ACPI: PCI interrupt 0000:02:09.0[A] ->
GSI 11 (level, low) -> IRQ 11
Apr 24 08:40:49 linux kernel: Restarting tasks...<6>usb 3-2: USB
disconnect, address 2
Apr 24 08:40:49 linux kernel:  done
Apr 24 08:40:50 linux kernel:   Enabling hardware tapping
Apr 24 08:40:50 linux kernel: usb 3-2: new low speed USB device using
uhci_hcd and address 3
Apr 24 08:40:50 linux su: (to jrh) root on none
Apr 24 08:40:50 linux kernel: input: USB HID v1.10 Mouse [Logitech USB
Receiver] on usb-0000:00:1d.1-2
Apr 24 08:40:50 linux kernel: input: DualPoint Stick on isa0060/serio1
Apr 24 08:40:50 linux kernel: input: AlpsPS/2 ALPS DualPoint TouchPad
on isa0060/serio1
Apr 24 08:41:05 linux gconfd (jrh-9358): Received signal 15, shutting
down cleanly
Apr 24 08:41:05 linux gconfd (jrh-9358): Exiting
Apr 24 08:41:07 linux init: Switching to runlevel: 0

5.Remove keyboard without risk of shutting system down.

I managed to totally screw up the USB keyboard the other day on my Blade 
2000. I've stuck one on which was one I tried to modify from US - >UK. 
That was never successful, so has some keys missing, like the pipe! I 
can just about use it though.

I have a type 7 on order. Is it possible to remove the old keyboard and 
fit the new one without risk of shutting the system down? I believe the 
escape sequence can be changed. Will that allow me to prevent it 
crashing while I replace the keyboard? I've got something running which 
will take two weeks to finish, but I don't want to wait 2 weeks before i 
change the keyboard.

Dave

6. halt and poweroff do not shut the system down

7. halt does not shut the system down

8. system hangs on "turning off swap"



Return to unix

 

Who is online

Users browsing this forum: No registered users and 6 guest