#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
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
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
** 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.
** 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 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:
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,
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
** 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
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
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
** 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)
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
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
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
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
16 matches
Mail list logo
