If i use mock clean, does it break the data of koji ?
I forgot to mention I use koji instead of use mock directly!
This morning i want to start httpd and kojid , but ...
[eric@wenjia ~]$ sudo service httpd restart
stop httpd： [OK]
starting httpd：httpd: apr_sockaddr_info_get() failed for wenjia.zhong
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[eric@wenjia conf]$ sudo service kojid start
starting kojid：Traceback (most recent call last):
File "/usr/sbin/kojid", line 3450, in <module>
File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 1458, in ssl_login
sinfo = self.callMethod('sslLogin', proxyuser)
File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 1503, in callMethod
return self._callMethod(name, args, opts)
File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 1548, in _callMethod
xmlrpclib.Fault: <Fault 1: "<class 'socket.gaierror'>: [Errno -2] Name or service not known">
when i set ServerName = 10.3.0.96:80 (my LAN IP ) , the httpd can be started successfull.
but the kojid return the same info.
Very strangely ! I think some thing Wrong in koji !!!
Is it crash ？
If i reinstall koji ,the data in DB will be delete? Import the srpm and rpm will spend a lot of time.
Please give some advise!2010/3/31 Mike McLean <email@example.com>
On 03/31/2010 05:12 AM, Paul Howarth wrote:For a number of chroot operations (e.g. building), mock uses an
> The /var/lib/mock/dist-foo-build-18-13 directory may be a hangover from
> when things were broken previously. It shouldn't be owned by user "torrent".
> I'd do an "ls -l /var/lib/mock" and move any directories owned by user
> "torrent" somewhere else, then try again. If everything then works OK,
> delete the moved directories (mock should re-create these directories as
unprivileged user it creates in the chroot. By default, the uid/gid for
this unprivileged user is chosen based on the user running mock (it
looks at env data from sudo/consolehelper to determine the real user).
So, the builddir in the chroot is going to be owned by that unprivileged
user. If you run mock as a /different/ user later and attempt to reuse
the same buildroot, then you will get the errors like the ones you are
Short answer: different mock users cannot share chroots.
Easy fix: run mock clean to clear the old junk out of the buildroot.
buildsys mailing list