Re: Some problems with the mythtv 0.25 upgrade

トップ ページ

このメッセージに返信
著者: Ross Boylan
日付:  
To: Christian Marillat
CC: RossBoylan, dmo-discussion
題目: Re: Some problems with the mythtv 0.25 upgrade
On Mon, 2012-05-14 at 08:21 +0200, Christian Marillat wrote:
> Ross Boylan <RossBoylan@???> writes:
>
> Apparently you have lost the subscription to the dmo-discussion list or
> you was subscribed with another address.
>
> [...]
>

That's odd. I resubscribed with the new list domain.

> > A couple of comments: the logs seem to show myth recognizes the current
> > schema is old. Does this mean it made contact with the database? Or
> > does it reflect information stored somwhere else?
> >
> > I can't find (e.g., dpkg -S, dpkg -L)
> > mythplugins/mythvideo/README.database
>
> Could you try to remove the mythvideo package ?
>
> Christian

mythvideo is not installed, and the only version showing in aptitude is
0.24.

By the way, does the 0.24->0.25 upgrade process leave a backup of the
0.24 database anywhere?

I notice some other activity at the same time as the myth upgrade. This
does create the messagebus user; perhaps that somehow had something to
do with the owner of mysql.text becoming messagebus (?). I'm not sure
if useradd will leak from the chroot to the main system, or conversely
if the host systems user info somehow gets into the chroot.

Host system:
messagebus:x:101:104::/var/run/dbus:/bin/false
bind:x:102:111::/var/cache/bind:/bin/false
mythtv:x:999:999::/var/lib/mythtv:/bin/sh

chroot:
mysql:x:101:102:MySQL Server,,,:/var/lib/mysql:/bin/false
mythtv:x:999:999::/var/lib/mythtv:/bin/sh
messagebus:x:102:105::/var/run/dbus:/bin/false

So mythtv is the same in both (I manually created it in the host to be
sure that was true) and messagebus is not. But it doesn't look as if
any confusion could cause mythtv to be mistaken for message bus.

Maybe something in the name resolution got messed up with mDNS?

Finally, /etc/hostname is corn-testing in the chroot, but when the host
syslog records messages from the chroot they are identified as corn.

Here are high points of syslog from the upgrade:
May 12 08:46:17 corn groupadd[18377]: group added to /etc/group: name=messagebus, GID=105
May 12 08:46:17 corn groupadd[18377]: group added to /etc/gshadow: name=messagebus
May 12 08:46:17 corn groupadd[18377]: new group: name=messagebus, GID=105
May 12 08:46:17 corn useradd[18381]: new user: name=messagebus, UID=102, GID=105, home=/var/run/dbus, shell=/bin/false
May 12 08:46:17 corn usermod[18386]: change user 'messagebus' password
May 12 08:46:17 corn chage[18391]: changed password expiry for messagebus
May 12 08:46:18 corn groupadd[18431]: group added to /etc/group: name=avahi, GID=106
May 12 08:46:18 corn groupadd[18431]: group added to /etc/gshadow: name=avahi
May 12 08:46:18 corn groupadd[18431]: new group: name=avahi, GID=106
May 12 08:46:18 corn useradd[18435]: new user: name=avahi, UID=103, GID=106, home=/var/run/avahi-daemon, shell=/bin/false
May 12 08:46:18 corn usermod[18440]: change user 'avahi' password
May 12 08:46:18 corn chage[18445]: changed password expiry for avahi
May 12 08:46:18 corn chfn[18448]: changed user 'avahi' information
May 12 08:46:18 corn groupadd[18453]: group added to /etc/group: name=netdev, GID=107
May 12 08:46:18 corn groupadd[18453]: group added to /etc/gshadow: name=netdev
May 12 08:46:18 corn groupadd[18453]: new group: name=netdev, GID=107
May 12 08:46:18 corn dbus[18426]: [system] Reloaded configuration
May 12 08:46:18 corn dbus[18426]: [system] Reloaded configuration
May 12 08:46:18 corn avahi-daemon[18503]: Found user 'avahi' (UID 103) and group 'avahi' (GID 106).
May 12 08:46:18 corn avahi-daemon[18503]: Successfully dropped root privileges.
May 12 08:46:18 corn avahi-daemon[18503]: avahi-daemon 0.6.31 starting up.
May 12 08:46:18 corn avahi-daemon[18503]: Successfully called chroot().
May 12 08:46:18 corn avahi-daemon[18503]: Successfully dropped remaining capabilities.
May 12 08:46:18 corn avahi-daemon[18503]: No service file found in /etc/avahi/services.
May 12 08:46:18 corn avahi-daemon[18503]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
May 12 08:46:18 corn avahi-daemon[18503]: *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
May 12 08:46:18 corn avahi-daemon[18503]: Joining mDNS multicast group on interface ethslow.IPv6 with address fe80::20e:cff:fe9b:e884.
May 12 08:46:18 corn avahi-daemon[18503]: New relevant interface ethslow.IPv6 for mDNS.
May 12 08:46:18 corn avahi-daemon[18503]: Joining mDNS multicast group on interface ethslow.IPv4 with address 66.181.128.6.
May 12 08:46:18 corn avahi-daemon[18503]: New relevant interface ethslow.IPv4 for mDNS.
May 12 08:46:18 corn avahi-daemon[18503]: Joining mDNS multicast group on interface ethfast.IPv6 with address fe80::213:20ff:feb7:2353.
May 12 08:46:18 corn avahi-daemon[18503]: New relevant interface ethfast.IPv6 for mDNS.
May 12 08:46:18 corn avahi-daemon[18503]: Joining mDNS multicast group on interface ethfast.IPv4 with address 192.168.40.3.
May 12 08:46:18 corn avahi-daemon[18503]: New relevant interface ethfast.IPv4 for mDNS.
May 12 08:46:18 corn avahi-daemon[18503]: Network interface enumeration completed.
May 12 08:46:18 corn avahi-daemon[18503]: Registering new address record for fe80::20e:cff:fe9b:e884 on ethslow.*.
May 12 08:46:18 corn avahi-daemon[18503]: Registering new address record for 66.181.128.6 on ethslow.IPv4.
May 12 08:46:18 corn avahi-daemon[18503]: Registering new address record for fe80::213:20ff:feb7:2353 on ethfast.*.
May 12 08:46:18 corn avahi-daemon[18503]: Registering new address record for 192.168.40.3 on ethfast.IPv4.
May 12 08:46:18 corn avahi-daemon[18503]: Registering new address record for 192.168.40.2 on ethfast.IPv4.
May 12 08:46:18 corn avahi-daemon[18503]: Registering HINFO record with values 'I686'/'LINUX'.
May 12 08:46:19 corn avahi-daemon[18503]: Server startup complete. Host name is corn.local. Local service cookie is 1234xxx.