[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] Segfault in libvirtd when run as a service



On Thu, Jun 10, 2010 at 2:05 PM, Matthias Bolte <matthias bolte googlemail com> wrote:
2010/6/10 Emre Erenoglu <erenoglu gmail com>:
> Dear list,
>
> I'm trying to package libvirt 0.8.1 for our distribution, Pardus 2009.2.
> libvirt is installed perfectly normal, and libvirtd runs OK when I start it
> in a console using root account.
>
> However, when I start libvirtd as a service, with the same parameters,
> through the normal service startup functions, it segfaults.
>
> The services in Pardus 2009.2 are started using a management backend which
> works with python and service start/stop scripts are python based.
>
> For libvirt, it's the following:
> http://svn.pardus.org.tr/pardus/playground/ozan/libvirt/comar/service.py
>
> Whatever I did, I couldn't find why libvirt is crashing. It works normal
> when I run it from console with exactly the same parameters. Here's an
> earlier syslog section ending with the crash:
>

There are some things to consider:

- Did you use the exact same commandline as the initscript when
testing manually?

Yes. In fact, the only parameter passed is the --daemon parameter with current configuration.
 
- Did you make sure to use the same environment variable configuration when starting libvirtd manually, compared to the initscript?

Here's the environment of the root user, I will try to find out the environment of the service script:


MANPATH=/usr/local/share/man:/usr/share/man:/opt/sun-jre/man:/usr/kde/4/share/man
HOSTNAME=EMRE
SHELL=/bin/bash
TERM=linux
XDG_SESSION_COOKIE=3d6ade2bb28141896f3212d64bf41670-1276174999.886063-1263776093
HUSHLOGIN=FALSE
LC_ALL=en_US.UTF-8
USER=root
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.pisi=01;33:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.ogv=01\:35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.pdf=00;32:*.ps=00;32:*.txt=00;32:*.patch=00;32:*.diff=00;32:*.log=00;32:*.tex=00;32:*.doc=00;32:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:
GUILE_LOAD_PATH=/usr/share/guile/1.8
MC_ENV=/usr/share/mc/bin/mc.sh
PAGER=/usr/bin/less
CONFIG_PROTECT_MASK=/etc/texmf/web2c /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/opt/sun-jre/bin:/usr/kde/4/sbin:/usr/kde/4/bin
PWD=/root
JAVA_HOME=/opt/sun-jre
EDITOR=/bin/nano
LESSCOLOR=yes
LANG=en_US.UTF-8
PYTHONSTARTUP=/etc/pythonstart
PS1=\[\033[1;31m\]\h \[\033[1;34m\]\W \$ \[\033[00m\]
SHLVL=1
HOME=/root
LD_BIND_DIRECT=1
LESS=-R -M --shift 5
LOGNAME=root
CVS_RSH=ssh
XDG_DATA_DIRS=/usr/kde/4/share:/usr/share
PKG_CONFIG_PATH=/usr/kde/4/lib/pkgconfig:/usr/qt/4/lib/pkgconfig
LESSOPEN=|lesspipe.sh %s
INFOPATH=/usr/share/info
LADSPA_PATH=/usr/lib/ladspa
SANE_CONFIG_DIR=/etc/sane.d
_=/usr/bin/env

Do you see any environment variable that may affect behaviour of libvirtd?

Could you provide a GDB backtrace of the segfault? The syslog entry only says that it crashed in libc, that's not enough information to
debug the segfault.

Unfortunately, I can't find a related core file in the system. In fact, core file is not generated. I'll also try to fix this out and come back to the list.

Thanks a lot,

Emre


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]