[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
#0 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) where #0 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8f43781b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f8f46bcf53b in dump_core () at lib/fault.c:391 #3 0x7f8f46bddc01 in smb_panic (why=optimized out) at lib/util.c:1133 #4 0x7f8f46bcee88 in fault_report (sig=6) at lib/fault.c:53 #5 sig_fault (sig=6) at lib/fault.c:76 #6 signal handler called #7 0x7f8f4377e425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7f8f43781b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7f8f437bc39e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x7f8f437c6b96 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x7f8f45f1bb78 in gss_release_buffer () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #12 0x7f8f46c4b182 in gse_get_pac_blob (gse_ctx=optimized out, mem_ctx=0x7f8f4778a4e0, pac_blob=optimized out) at librpc/crypto/gse.c:731 #13 0x7f8f46ae21ab in gssapi_server_get_user_info (gse_ctx=0x7f8f47790030, mem_ctx=0x7f8f47786660, client_id=0x7f8f477705e8, server_info=0x7f8f47786688) at rpc_server/dcesrv_gssapi.c:127 #14 0x7f8f46ad667d in pipe_gssapi_verify_final (mem_ctx=0x7f8f47786660, gse_ctx=0x7f8f47790030, client_id=0x7f8f477705e8, session_info=0x7f8f47786688) at rpc_server/srv_pipe.c:734 #15 0x7f8f46ad806a in pipe_auth_verify_final (p=0x7f8f47786660) at rpc_server/srv_pipe.c:814 #16 0x7f8f46ada25b in api_pipe_alter_context (pkt=0x7f8f47790f30, p=0x7f8f47786660) at rpc_server/srv_pipe.c:1403 #17 process_complete_pdu (p=0x7f8f47786660) at rpc_server/srv_pipe.c:1955 #18 0x7f8f46ada94b in process_incoming_data (p=0x7f8f47786660, data=0x7f8f47792db4 \270\020\270\020, n=optimized out) at rpc_server/srv_pipe_hnd.c:218 #19 0x7f8f46adb02e in write_to_internal_pipe (n=177, data=0x7f8f47792db4 \270\020\270\020, p=0x7f8f47786660) at rpc_server/srv_pipe_hnd.c:244 #20 np_write_send (mem_ctx=optimized out, ev=0x7f8f47770520, handle=optimized out, data=optimized out, len=177) at rpc_server/srv_pipe_hnd.c:538 #21 0x7f8f468ef967 in reply_pipe_write_and_X (req=0x7f8f47792eb0) at smbd/pipes.c:322 #22 0x7f8f468f9308 in reply_write_and_X (req=0x7f8f47792eb0) at smbd/reply.c:4529 #23 0x7f8f4693bfa4 in switch_message (type=47 '/', req=0x7f8f47792eb0, size=245) at smbd/process.c:1574 #24 0x7f8f4693c3bb in construct_reply (deferred_pcd=0x0, encrypted=false, seqnum=optimized out, unread_bytes=0, size=245, inbuf=0x0, sconn=0x7f8f477705e0) at smbd/process.c:1610 #25 process_smb (sconn=0x7f8f477705e0, inbuf=optimized out, nread=245, unread_bytes=0, seqnum=optimized out, encrypted=false, deferred_pcd=0x0) at smbd/process.c:1688 #26 0x7f8f4693c7d3 in smbd_server_connection_read_handler (conn=0x7f8f477705e0, fd=24) at smbd/process.c:2317 #27 0x7f8f46bed8ae in run_events_poll (num_pfds=2, pfds=0x7f8f4777b040, pollrtn=optimized out, ev=0x7f8f47770520) at lib/events.c:286 #28 run_events_poll (ev=0x7f8f47770520, pollrtn=optimized out, pfds=0x7f8f4777b040, num_pfds=2) at lib/events.c:184 #29 0x7f8f4693df42 in smbd_server_connection_loop_once (conn=0x7f8f477705e0) at smbd/process.c:1017 #30 smbd_process (sconn=0x7f8f477705e0) at smbd/process.c:3158 #31 0x7f8f46e4b66f in smbd_accept_connection (ev=optimized out, fde=optimized out, flags=optimized out, private_data=optimized out) at smbd/server.c:511 #32 0x7f8f46bed8ae in run_events_poll (num_pfds=3, pfds=0x7f8f477732e0, pollrtn=optimized out, ev=0x7f8f47770520) at lib/events.c:286 #33 run_events_poll (ev=0x7f8f47770520, pollrtn=optimized out, pfds=0x7f8f477732e0, num_pfds=3) at lib/events.c:184 #34 0x7f8f46beda4a in s3_event_loop_once (ev=0x7f8f47770520, location=optimized out) at lib/events.c:349 #35 0x7f8f46bee5d0 in _tevent_loop_once (ev=0x7f8f47770520, location=0x7f8f470502d7 smbd/server.c:844) at ../lib/tevent/tevent.c:494 #36 0x7f8f468bc030 in smbd_parent_loop (parent=optimized out) at smbd/server.c:844 #37 main (argc=optimized out, argv=optimized out) at smbd/server.c:1326 ** Attachment removed: logs, configs https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+attachment/3470091/+files/sambaerr.tar.gz ** Changed in: samba (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
I have installed samba-dbg and dbg packages. If I can help to debug this problem, tell me what to do. Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] [NEW] Samba crashes invalid pointer: 0x00007f0bc3de7590
Public bug reported: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Attachment added: logs, configs https://bugs.launchpad.net/bugs/1094438/+attachment/3470091/+files/sambaerr.tar.gz ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain + Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. Samba crushes after opening shared folder from windows workstation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. - Samba crushes after opening shared folder from windows workstation. + We have 2 same server with same config (differents only in hostname). + + Samba crushes after opening shared folder from windows workstation on + both servers. ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. - We have 2 same server with same config (differents only in hostname). + We have two of the same server with the same configuration (differents + only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. ** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). Samba crushes after opening shared folder from windows workstation on both servers. + + BACKTRACE: 30 stack frames: +#0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] +#1 smbd(smb_panic+0x25) [0x7f4533d61bc5] +#2 smbd(+0x409e88) [0x7f4533d52e88] +#3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] +#4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] +#5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] +#6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] +#7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] +#8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] +#9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] +#10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] +#11 smbd(+0x31167d) [0x7f4533c5a67d] +#12 smbd(+0x31306a) [0x7f4533c5c06a] +#13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] +#14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] +#15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] +#16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] +#17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] +#18 smbd(+0x176fa4) [0x7f4533abffa4] +#19 smbd(+0x1773bb) [0x7f4533ac03bb] +#20 smbd(+0x1777d3) [0x7f4533ac07d3] +#21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] +#22 smbd(smbd_process+0x812) [0x7f4533ac1f42] +#23 smbd(+0x68666f) [0x7f4533fcf66f] +#24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] +#25 smbd(+0x428a4a) [0x7f4533d71a4a] +#26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] +#27 smbd(main+0xed0) [0x7f4533a40030] +#28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] +#29 smbd(+0xf7515) [0x7f4533a40515] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
** Description changed: Ubuntu 12.04.1 LTS Samba 2:3.6.3-2ubuntu2.3 krb5-config 2.2 Samba on ubuntu joined to Windows 2003 domain Share on /media/100RAGE = /dev/md0 (software raid5) getent passwd, getent group working fine. All working fine, except I see errors in samba logs. We have two of the same server with the same configuration (differents only in hostname). - Samba crushes after opening shared folder from windows workstation on - both servers. + Samba crushes everytime after opening shared folder from windows + workstation on both servers. - BACKTRACE: 30 stack frames: -#0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] -#1 smbd(smb_panic+0x25) [0x7f4533d61bc5] -#2 smbd(+0x409e88) [0x7f4533d52e88] -#3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] -#4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] -#5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] -#6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] -#7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] -#8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] -#9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] -#10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] -#11 smbd(+0x31167d) [0x7f4533c5a67d] -#12 smbd(+0x31306a) [0x7f4533c5c06a] -#13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] -#14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] -#15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] -#16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] -#17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] -#18 smbd(+0x176fa4) [0x7f4533abffa4] -#19 smbd(+0x1773bb) [0x7f4533ac03bb] -#20 smbd(+0x1777d3) [0x7f4533ac07d3] -#21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] -#22 smbd(smbd_process+0x812) [0x7f4533ac1f42] -#23 smbd(+0x68666f) [0x7f4533fcf66f] -#24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] -#25 smbd(+0x428a4a) [0x7f4533d71a4a] -#26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] -#27 smbd(main+0xed0) [0x7f4533a40030] -#28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] -#29 smbd(+0xf7515) [0x7f4533a40515] + BACKTRACE: 30 stack frames: + #0 smbd(log_stack_trace+0x1a) [0x7f4533d61aea] + #1 smbd(smb_panic+0x25) [0x7f4533d61bc5] + #2 smbd(+0x409e88) [0x7f4533d52e88] + #3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f45309024a0] + #4 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f4530902425] + #5 /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f4530905b8b] + #6 /lib/x86_64-linux-gnu/libc.so.6(+0x7439e) [0x7f453094039e] + #7 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96) [0x7f453094ab96] + #8 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2(gss_release_buffer+0x28) [0x7f453309fb78] + #9 smbd(gse_get_pac_blob+0x202) [0x7f4533dcf182] + #10 smbd(gssapi_server_get_user_info+0x6b) [0x7f4533c661ab] + #11 smbd(+0x31167d) [0x7f4533c5a67d] + #12 smbd(+0x31306a) [0x7f4533c5c06a] + #13 smbd(process_complete_pdu+0x102b) [0x7f4533c5e25b] + #14 smbd(process_incoming_data+0x12b) [0x7f4533c5e94b] + #15 smbd(np_write_send+0x14e) [0x7f4533c5f02e] + #16 smbd(reply_pipe_write_and_X+0x167) [0x7f4533a73967] + #17 smbd(reply_write_and_X+0x368) [0x7f4533a7d308] + #18 smbd(+0x176fa4) [0x7f4533abffa4] + #19 smbd(+0x1773bb) [0x7f4533ac03bb] + #20 smbd(+0x1777d3) [0x7f4533ac07d3] + #21 smbd(run_events_poll+0x34e) [0x7f4533d718ae] + #22 smbd(smbd_process+0x812) [0x7f4533ac1f42] + #23 smbd(+0x68666f) [0x7f4533fcf66f] + #24 smbd(run_events_poll+0x34e) [0x7f4533d718ae] + #25 smbd(+0x428a4a) [0x7f4533d71a4a] + #26 smbd(_tevent_loop_once+0x90) [0x7f4533d725d0] + #27 smbd(main+0xed0) [0x7f4533a40030] + #28 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f45308ed76d] + #29 smbd(+0xf7515) [0x7f4533a40515] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
samba 2:3.6.6-3ubuntu5 from quantal installed in 12.04 = no probles! No coredumps. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978356] Re: squid3 gets killed at startup with dnsmasq and no networkmanager
Fixed for me: Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/978356 Title: squid3 gets killed at startup with dnsmasq and no networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/978356/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 995523] Re: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
This bug also fixed by patch in bug #978356 Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978356] Re: squid3 gets killed at startup with dnsmasq and no networkmanager
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/978356 Title: squid3 gets killed at startup with dnsmasq and no networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/978356/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 988802] Re: squid3 killed by ABRT signal. assertion failed: disk.cc377: fd = 0
This bug also fixed by patch in bug #978356 Jun 23 00:04:44 server kernel: [ 14.922376] init: squid3 main process (1148) killed by ABRT signal Jun 23 00:04:44 server kernel: [ 14.922405] init: squid3 main process ended, respawning -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/988802 Title: squid3 killed by ABRT signal. assertion failed: disk.cc377: fd = 0 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/988802/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839490] Re: NUT is not shutdown UPS
I have nut version 2.6.0-1ubuntu3 upsmon forks 2 instances - yes, I have they. But why killpower is setting by unprivileded instance (nut)? I confirm, SHUTDOWNCMD is launched proper (by privileged instance). I have 3 servers on Ubuntu 11.04 with UPS APC on each. Config files,daemons are identical. Differents only in UPS. APC SmartUPS 750i (SUA750I), BackUPS CS 500 (BK500EI), BackUPS ES 550. All connected with driver = usbhid-ups. So, many info: root@gwlin:/etc/nut# ps faux | grep ups root 231 0.0 0.1 2412 556 ?SSep03 0:00 upstart-udev-bridge --daemon root 668 0.0 0.0 2412 468 ?SSep03 0:00 upstart-socket-bridge --daemon root 12368 0.0 0.1 5304 852 pts/1S+ 15:22 0:00 \_ grep --color=auto ups nut 2510 0.0 0.0 2196 444 ?Ss Sep03 5:20 /lib/nut/usbhid-ups -a ippon nut 2512 0.0 0.0 2128 456 ?Ss Sep03 0:53 /sbin/upsd root 2514 0.0 0.1 2108 568 ?Ss Sep03 0:00 /sbin/upsmon nut 2516 0.0 0.1 2108 576 ?SSep03 0:30 \_ /sbin/upsmon root@gwlin:/etc/nut# cat /etc/nut/nut.conf | egrep -v (^#.*|^$) MODE=netserver root@gwlin:/etc/nut# cat /etc/nut/ups.conf | egrep -v (^#.*|^$) [ippon] driver = usbhid-ups port = auto root@gwlin:/etc/nut# cat /etc/nut/upsd.conf | egrep -v (^#.*|^$) LISTEN 127.0.0.1 LISTEN 10.0.0.1 root@gwlin:/etc/nut# cat /etc/nut/upsd.users | egrep -v (^#.*|^$) [local_mon] password = XX upsmon master [server_mon] password = XX upsmon slave [root] password = XX actions = SET instcmds = ALL root@gwlin:/etc/nut# cat /etc/nut/upsmon.conf | egrep -v (^#.*|^$) MONITOR ippon@localhost 1 local_mon XX master MINSUPPLIES 1 SHUTDOWNCMD /sbin/shutdown -h +0 NOTIFYCMD /usr/local/bin/upsmail POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/nut/killpower NOTIFYFLAG ONLINE EXEC+SYSLOG NOTIFYFLAG ONBATT EXEC+SYSLOG NOTIFYFLAG LOWBATT EXEC+SYSLOG NOTIFYFLAG FSD EXEC+SYSLOG NOTIFYFLAG COMMOK EXEC+SYSLOG NOTIFYFLAG COMMBAD EXEC+SYSLOG NOTIFYFLAG SHUTDOWN EXEC+SYSLOG NOTIFYFLAG REPLBATT EXEC+SYSLOG NOTIFYFLAG NOCOMM EXEC+SYSLOG RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 root@gwlin:/etc/default# cat ./halt | egrep -v (^#.*|^$) HALT=poweroff root@gwlin:/etc/init.d# upsmon -K Network UPS Tools upsmon 2.6.0 UPS: ippon@localhost (master) (power value 1) Using power down flag file /etc/nut/killpower Power down flag is not set -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839490] Re: NUT is not shutdown UPS
** Description changed: Description:Ubuntu 11.04 Release:11.04 nut version 2.6.0-1ubuntu3 - Problem: + Problem: upsmon working under nut user (not root). nut user can't create file /etc/killpower Example: 1) Mains out. UPS on battery 2) Battery low. set FSD 3) upsmon executes shutdowncmd but fails to create /etc/killpower 4) /etc/init.d/halt executes /etc/init.d/ups-monitor poweroff 5) /etc/init.d/ups-monitor poweroff executes upsmon -K to check /etc/killpower (but file does not exist) 6) not sending shutdown command to UPS (upsdrvctl shutdown is not executed) 7) system halted, but UPS stays on battery 8) mains come back, ups going on mains, but load is not switched off/on - 9) PC stay OFF (need manual start) + 9) PC stays OFF (need manual start) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839490] [NEW] NUT is not shutdown UPS
Public bug reported: Description:Ubuntu 11.04 Release:11.04 nut version 2.6.0-1ubuntu3 Problem: upsmon working under nut user (not root). nut user can't create file /etc/killpower Example: 1) Mains out. UPS on battery 2) Battery low. set FSD 3) upsmon executes shutdowncmd but fails to create /etc/killpower 4) /etc/init.d/halt executes /etc/init.d/ups-monitor poweroff 5) /etc/init.d/ups-monitor poweroff executes upsmon -K to check /etc/killpower (but file does not exist) 6) not sending shutdown command to UPS (upsdrvctl shutdown is not executed) 7) system halted, but UPS stays on battery 8) mains come back, ups going on mains, but load is not switched off/on 9) PC stay OFF (need manual start) ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839490] Re: NUT is not shutdown UPS
Temp. solution: 1) rm -f /etc/killpower 2) chmod -R g+w /etc/nut/ 3) edit upsmon.conf and change POWERDOWNFLAG /etc/nut/killpower 4) service nut restart After this all fine! UPS shutdowns correctly. PC starts up when UPS goes on. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839490 Title: NUT is not shutdown UPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839490/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839509] [NEW] nut can not log to syslog when shutdown
Public bug reported: Ubuntu 11.04 NUT 2.6.0 System shutting down (battery low, FSD set) and executes /etc/init.d /ups-monitor poweroff ups-monitor script contains section poweroff. in this section we can see log_daemon_msg which sends info to syslog but rsyslogd already stopped. This is in syslog when shutdown: Sep 2 17:37:58 gwlin upsmon[1229]: Signal 10: User requested FSD Sep 2 17:37:58 gwlin upsd[1225]: Client local_mon@127.0.0.1 set FSD on UPS [ippon] Sep 2 17:37:58 gwlin upsmon[1229]: Executing automatic power-fail shutdown Sep 2 17:37:58 gwlin upsmon[1229]: Auto logout and shutdown proceeding Sep 2 17:38:03 gwlin kernel: Kernel logging (proc) stopped. Sep 2 17:38:03 gwlin rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=374 x-info=http://www.rsyslog.com;] exiting on signal 15. ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 839509] Re: nut can not log to syslog when shutdown
Sorry. Expected messages like Shutting down the UPS ..., Waiting for UPS to cut the power, ... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/839509 Title: nut can not log to syslog when shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/839509/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
