[gentoo-user] emerging squid indefinitely

[gentoo-user] emerging squid indefinitely

[lee]

Hi,

emerging squid doesn't seem to ever finish:


[...]
>>> Emerging (9 of 9) net-proxy/squid-3.5.6::gentoo
>>> Jobs: 8 of 9 complete, 1 running                Load avg: 0.37, 0.61, 0.53


What would I look at, without interrupting emerge, to find out what's
going on?

Re: [gentoo-user] emerging squid indefinitely

[Alan McKinnon]

On 23/11/2015 17:02, lee wrote:
> 
> Hi,
> 
> emerging squid doesn't seem to ever finish:
> 
> 
> [...]
>>>> Emerging (9 of 9) net-proxy/squid-3.5.6::gentoo
>>>> Jobs: 8 of 9 complete, 1 running                Load avg: 0.37, 0.61, 0.53
> 
> 
> What would I look at, without interrupting emerge, to find out what's
> going on?
> 


tail the build log



-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] emerging squid indefinitely

[lee]

Alan McKinnon <alan.mckinnon@gmail.com> writes:

> On 23/11/2015 17:02, lee wrote:
>> 
>> Hi,
>> 
>> emerging squid doesn't seem to ever finish:
>> 
>> 
>> [...]
>>>>> Emerging (9 of 9) net-proxy/squid-3.5.6::gentoo
>>>>> Jobs: 8 of 9 complete, 1 running                Load avg: 0.37, 0.61, 0.53
>> 
>> 
>> What would I look at, without interrupting emerge, to find out what's
>> going on?
>> 
>
>
> tail the build log

Which is where?  There isn't anything in
/var/log/portage/elog/summary.log, and /var/log/emerge.log only says:


1448288177:  ::: completed emerge (8 of 9) net-libs/gnutls-3.3.17.1 to /
1448288177:  >>> emerge (9 of 9) net-proxy/squid-3.5.6 to /
1448288177:  === (9 of 9) Cleaning (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
1448288177:  === (9 of 9) Compiling/Merging (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)


It's still pretending that it's compiling, hours later ...

Re: [gentoo-user] emerging squid indefinitely

[Todd Goodman]

* lee <lee@yagibdah.de> [151123 16:05]:
> Alan McKinnon <alan.mckinnon@gmail.com> writes:
> 
> > On 23/11/2015 17:02, lee wrote:
> >> 
> >> Hi,
> >> 
> >> emerging squid doesn't seem to ever finish:
> >> 
> >> 
> >> [...]
> >>>>> Emerging (9 of 9) net-proxy/squid-3.5.6::gentoo
> >>>>> Jobs: 8 of 9 complete, 1 running                Load avg: 0.37, 0.61, 0.53
> >> 
> >> 
> >> What would I look at, without interrupting emerge, to find out what's
> >> going on?
> >> 
> >
> >
> > tail the build log
> 
> Which is where?  There isn't anything in
> /var/log/portage/elog/summary.log, and /var/log/emerge.log only says:
> 
> 
> 1448288177:  ::: completed emerge (8 of 9) net-libs/gnutls-3.3.17.1 to /
> 1448288177:  >>> emerge (9 of 9) net-proxy/squid-3.5.6 to /
> 1448288177:  === (9 of 9) Cleaning (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
> 1448288177:  === (9 of 9) Compiling/Merging (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
> 
> 
> It's still pretending that it's compiling, hours later ...

It should be at /var/tmp/portage/net-proxy/squid-3.5.6/temp/build.log.

Todd

Re: [gentoo-user] emerging squid indefinitely

[Alan McKinnon]

On 23/11/2015 23:04, lee wrote:
> Alan McKinnon <alan.mckinnon@gmail.com> writes:
> 
>> On 23/11/2015 17:02, lee wrote:
>>>
>>> Hi,
>>>
>>> emerging squid doesn't seem to ever finish:
>>>
>>>
>>> [...]
>>>>>> Emerging (9 of 9) net-proxy/squid-3.5.6::gentoo
>>>>>> Jobs: 8 of 9 complete, 1 running                Load avg: 0.37, 0.61, 0.53
>>>
>>>
>>> What would I look at, without interrupting emerge, to find out what's
>>> going on?
>>>
>>
>>
>> tail the build log
> 
> Which is where?  There isn't anything in
> /var/log/portage/elog/summary.log, and /var/log/emerge.log only says:
> 
> 
> 1448288177:  ::: completed emerge (8 of 9) net-libs/gnutls-3.3.17.1 to /
> 1448288177:  >>> emerge (9 of 9) net-proxy/squid-3.5.6 to /
> 1448288177:  === (9 of 9) Cleaning (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
> 1448288177:  === (9 of 9) Compiling/Merging (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
> 
> 
> It's still pretending that it's compiling, hours later ...
> 


the build logs are the same place they have always been, in
/var/tmp/portage/.....

that location is a symlink to:

/var/log/portage/<cat>:<pkg>-<ver>:<timestamp>.log

and that info is dumped to the console in volume every time emerge fails
for any reason.

/var/log/portage/elog/summary.log and /var/log/emerge.log are emerge's
logs and contains logs of what emerge is doing. You want build logs to
find out what make and gcc etc are doing.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] emerging squid indefinitely

[lee]

Alan McKinnon <alan.mckinnon@gmail.com> writes:

> On 23/11/2015 23:04, lee wrote:
>> Alan McKinnon <alan.mckinnon@gmail.com> writes:
>> 
>>> On 23/11/2015 17:02, lee wrote:
>>>>
>>>> Hi,
>>>>
>>>> emerging squid doesn't seem to ever finish:
>>>>
>>>>
>>>> [...]
>>>>>>> Emerging (9 of 9) net-proxy/squid-3.5.6::gentoo
>>>>>>> Jobs: 8 of 9 complete, 1 running                Load avg: 0.37, 0.61, 0.53
>>>>
>>>>
>>>> What would I look at, without interrupting emerge, to find out what's
>>>> going on?
>>>>
>>>
>>>
>>> tail the build log
>> 
>> Which is where?  There isn't anything in
>> /var/log/portage/elog/summary.log, and /var/log/emerge.log only says:
>> 
>> 
>> 1448288177:  ::: completed emerge (8 of 9) net-libs/gnutls-3.3.17.1 to /
>> 1448288177:  >>> emerge (9 of 9) net-proxy/squid-3.5.6 to /
>> 1448288177:  === (9 of 9) Cleaning (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
>> 1448288177:  === (9 of 9) Compiling/Merging (net-proxy/squid-3.5.6::/usr/portage/net-proxy/squid/squid-3.5.6.ebuild)
>> 
>> 
>> It's still pretending that it's compiling, hours later ...
>> 
>
>
> the build logs are the same place they have always been, in
> /var/tmp/portage/.....
>
> that location is a symlink to:
>
> /var/log/portage/<cat>:<pkg>-<ver>:<timestamp>.log
>
> and that info is dumped to the console in volume every time emerge fails
> for any reason.
>
> /var/log/portage/elog/summary.log and /var/log/emerge.log are emerge's
> logs and contains logs of what emerge is doing. You want build logs to
> find out what make and gcc etc are doing.

Cool, let's see what it does (It's still emerging.):


,----
| dawn ~ # cat /var/tmp/portage/net-proxy/squid-3.5.6/temp/build.log                                                                                                                                                                        
|  * Package:    net-proxy/squid-3.5.6
|  * Repository: gentoo
|  * Maintainer: eras@gentoo.org
|  * USE:        abi_x86_64 amd64 caps elibc_glibc htcp ipv6 kernel_linux pam ssl userland_GNU wccp wccpv2
|  * FEATURES:   preserve-libs sandbox userpriv usersandbox
|  * Adding group 'squid' to your system ...
|  *  - Groupid: next available
`----


,----
| dawn ~ # ps xa | grep gro
| 10563 pts/0    T      0:00 groupadd -r squid
| 11315 pts/0    S+     0:00 grep --colour=auto gro
| dawn ~ # 
`----


It shouldn't take /that/ long to add a group, not even for a system
group.


,----
| dawn ~ # grep squid /etc/group
| squid:x:245:
| dawn ~ # 
`----


So the group has already been created.  Let's create a test group:


,----
| dawn ~ # time groupadd -r test
| groupadd: cannot lock /etc/group; try again later.
| 
| real    0m15.003s
| user    0m0.000s
| sys     0m0.000s
| dawn ~ # grep test /etc/group
| dawn ~ # ls -la /etc/group*
| -rw-r--r-- 1 root root 552 Nov 23 15:16 /etc/group
| -rw------- 1 root root 539 Nov  8 19:23 /etc/group-
| -rw------- 1 root root   6 Nov 23 15:16 /etc/group.lock
| dawn ~ # 
`----


Well, ok, the file is still locked.

'group-' looks like a backup, and 'group.lock' contains 10563, which is
the pid of groupadd.  I'd think that's ok.

So what all does it take to create a system group?  I suppose I could
kill groupadd and the emerging might go on, though I wonder what the
problem might be and if something else besides making an entry to
/etc/group needs to be done.  What might require an indefinite delay
here?

Any ideas?

[gentoo-user] Re: emerging squid indefinitely

[walt]

On Tue, 24 Nov 2015 23:39:01 +0100
lee <lee@yagibdah.de> wrote:

>
> ...

 
> Well, ok, the file is still locked.
> 
> 'group-' looks like a backup, and 'group.lock' contains 10563, which
> is the pid of groupadd.  I'd think that's ok.
> 
> So what all does it take to create a system group?  I suppose I could
> kill groupadd and the emerging might go on, though I wonder what the
> problem might be and if something else besides making an entry to
> /etc/group needs to be done.  What might require an indefinite delay
> here?

Any unusual network activity?  (DNS lookups that shouldn't be
happening, etc.) 

Re: [gentoo-user] Re: emerging squid indefinitely

[lee]

walt <w41ter@gmail.com> writes:

> On Tue, 24 Nov 2015 23:39:01 +0100
> lee <lee@yagibdah.de> wrote:
>
>>
>> ...
>
>  
>> Well, ok, the file is still locked.
>> 
>> 'group-' looks like a backup, and 'group.lock' contains 10563, which
>> is the pid of groupadd.  I'd think that's ok.
>> 
>> So what all does it take to create a system group?  I suppose I could
>> kill groupadd and the emerging might go on, though I wonder what the
>> problem might be and if something else besides making an entry to
>> /etc/group needs to be done.  What might require an indefinite delay
>> here?
>
> Any unusual network activity?  (DNS lookups that shouldn't be
> happening, etc.) 

There's nothing suspicious in the firewall log and no unexpected DNS
queries.

The emerge before this one was apache, which I suppose also creates a
system group, and that worked just fine.

I'll probably reboot today or tomorrow because I need to have a
differently configured kernel running to be able to do some traffic
shaping.  If I do that, I'll probably just kill groupadd and see if the
merging continues.

Re: [gentoo-user] Re: emerging squid indefinitely

[Alan McKinnon]

On 25/11/2015 13:30, lee wrote:
> walt <w41ter@gmail.com> writes:
> 
>> On Tue, 24 Nov 2015 23:39:01 +0100
>> lee <lee@yagibdah.de> wrote:
>>
>>>
>>> ...
>>
>>  
>>> Well, ok, the file is still locked.
>>>
>>> 'group-' looks like a backup, and 'group.lock' contains 10563, which
>>> is the pid of groupadd.  I'd think that's ok.
>>>
>>> So what all does it take to create a system group?  I suppose I could
>>> kill groupadd and the emerging might go on, though I wonder what the
>>> problem might be and if something else besides making an entry to
>>> /etc/group needs to be done.  What might require an indefinite delay
>>> here?
>>
>> Any unusual network activity?  (DNS lookups that shouldn't be
>> happening, etc.) 
> 
> There's nothing suspicious in the firewall log and no unexpected DNS
> queries.

Ignore DNS, it has absolutely nothing to do with creating a group. A
common human trait in dealing with problems with unknown causes is to
start investigating all manner of weird and entirely unrelated things.

I suppose theoretically you might discover some interaction between them
in truly bizarre conditions but that's never something you entertain.
Much like you don't check the health of your dog when investigating a
flat type (protests about dogs biting tyres and getting stomach upsets
notwithstanding)

> The emerge before this one was apache, which I suppose also creates a
> system group, and that worked just fine.
> 
> I'll probably reboot today or tomorrow because I need to have a
> differently configured kernel running to be able to do some traffic
> shaping.  If I do that, I'll probably just kill groupadd and see if the
> merging continues.

The group is already created so kill groupadd. One of three things will
happen:

1. the emerge will continue. Do nothing
2. The emerge will fail with a groupadd error. Restart the emerge
3. Nothing will change. Kill the emerge and restart it

If the lockfile persists after killing groupadd, delete it.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: emerging squid indefinitely

[lee]

Alan McKinnon <alan.mckinnon@gmail.com> writes:

> On 25/11/2015 13:30, lee wrote:
>> walt <w41ter@gmail.com> writes:
>> 
>>> On Tue, 24 Nov 2015 23:39:01 +0100
>>> lee <lee@yagibdah.de> wrote:
>>>
>>>>
>>>> ...
>>>
>>>  
>>>> Well, ok, the file is still locked.
>>>>
>>>> 'group-' looks like a backup, and 'group.lock' contains 10563, which
>>>> is the pid of groupadd.  I'd think that's ok.
>>>>
>>>> So what all does it take to create a system group?  I suppose I could
>>>> kill groupadd and the emerging might go on, though I wonder what the
>>>> problem might be and if something else besides making an entry to
>>>> /etc/group needs to be done.  What might require an indefinite delay
>>>> here?
>>>
> [...]
>> I'll probably reboot today or tomorrow because I need to have a
>> differently configured kernel running to be able to do some traffic
>> shaping.  If I do that, I'll probably just kill groupadd and see if the
>> merging continues.
>
> The group is already created so kill groupadd. One of three things will
> happen:
>
> 1. the emerge will continue. Do nothing
> 2. The emerge will fail with a groupadd error. Restart the emerge
> 3. Nothing will change. Kill the emerge and restart it
>
> If the lockfile persists after killing groupadd, delete it.

Well, yes ... I just would like to know what the problem might be.

[gentoo-user] Re: emerging squid indefinitely

[walt]

On Wed, 25 Nov 2015 18:53:50 +0200
Alan McKinnon <alan.mckinnon@gmail.com> wrote:

> On 25/11/2015 13:30, lee wrote:
> > walt <w41ter@gmail.com> writes:
> >   
> >> On Tue, 24 Nov 2015 23:39:01 +0100
> >> lee <lee@yagibdah.de> wrote:
> >>  
> >>>
> >>> ...  
> >>

> >>
> >> Any unusual network activity?  (DNS lookups that shouldn't be
> >> happening, etc.)   
> > 
> > There's nothing suspicious in the firewall log and no unexpected DNS
> > queries.  
> 
> Ignore DNS, it has absolutely nothing to do with creating a group. A
> common human trait in dealing with problems with unknown causes is to
> start investigating all manner of weird and entirely unrelated things.

And Happy Thanksgiving to you, grouchy old fart living somewhere south
of the equator where no one celebrates Thanksgiving :)

IIRC I learned about DNS queries causing delays directly from you.

Well, maybe it was some other old fart on this list.

Re: [gentoo-user] Re: emerging squid indefinitely

[Alan McKinnon]

On 26/11/2015 02:03, walt wrote:
> On Wed, 25 Nov 2015 18:53:50 +0200
> Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>
>> On 25/11/2015 13:30, lee wrote:
>>> walt <w41ter@gmail.com> writes:
>>>
>>>> On Tue, 24 Nov 2015 23:39:01 +0100
>>>> lee <lee@yagibdah.de> wrote:
>>>>
>>>>>
>>>>> ...
>>>>
>
>>>>
>>>> Any unusual network activity?  (DNS lookups that shouldn't be
>>>> happening, etc.)
>>>
>>> There's nothing suspicious in the firewall log and no unexpected DNS
>>> queries.
>>
>> Ignore DNS, it has absolutely nothing to do with creating a group. A
>> common human trait in dealing with problems with unknown causes is to
>> start investigating all manner of weird and entirely unrelated things.
>
> And Happy Thanksgiving to you, grouchy old fart living somewhere south
> of the equator where no one celebrates Thanksgiving :)

That's true enough. But we do celebrate bloodletting day round about the 
same time (commemorates some battle or other), and most of the rest of 
the population celebrates thankstaking. Oh well
>
> IIRC I learned about DNS queries causing delays directly from you.
>
> Well, maybe it was some other old fart on this list.

There's enough of us old farts here, you can blame any one of us for 
anything and get away with it :-)

Alan

Re: [gentoo-user] Re: emerging squid indefinitely

[Alan McKinnon]

On 26/11/2015 01:33, lee wrote:
> Alan McKinnon <alan.mckinnon@gmail.com> writes:
>
>> On 25/11/2015 13:30, lee wrote:
>>> walt <w41ter@gmail.com> writes:
>>>
>>>> On Tue, 24 Nov 2015 23:39:01 +0100
>>>> lee <lee@yagibdah.de> wrote:
>>>>
>>>>>
>>>>> ...
>>>>
>>>>
>>>>> Well, ok, the file is still locked.
>>>>>
>>>>> 'group-' looks like a backup, and 'group.lock' contains 10563, which
>>>>> is the pid of groupadd.  I'd think that's ok.
>>>>>
>>>>> So what all does it take to create a system group?  I suppose I could
>>>>> kill groupadd and the emerging might go on, though I wonder what the
>>>>> problem might be and if something else besides making an entry to
>>>>> /etc/group needs to be done.  What might require an indefinite delay
>>>>> here?
>>>>
>> [...]
>>> I'll probably reboot today or tomorrow because I need to have a
>>> differently configured kernel running to be able to do some traffic
>>> shaping.  If I do that, I'll probably just kill groupadd and see if the
>>> merging continues.
>>
>> The group is already created so kill groupadd. One of three things will
>> happen:
>>
>> 1. the emerge will continue. Do nothing
>> 2. The emerge will fail with a groupadd error. Restart the emerge
>> 3. Nothing will change. Kill the emerge and restart it
>>
>> If the lockfile persists after killing groupadd, delete it.
>
> Well, yes ... I just would like to know what the problem might be.
>

I doubt you'll ever find out. Something went wrong, a process hung and 
it's likely a once off. Deal with it, move on.

Re: [gentoo-user] Re: emerging squid indefinitely

[Peter Humphrey]

On Wednesday 25 November 2015 16:03:57 walt wrote:

> And Happy Thanksgiving to you, grouchy old fart living somewhere south
> of the equator where no one celebrates Thanksgiving :)

If I'm not mistaken, Thanksgiving is a purely US occasion  :)

-- 
Rgds
Peter

Re: [gentoo-user] Re: emerging squid indefinitely

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 414 bytes --]

On Wed, 25 Nov 2015 16:03:57 -0800, walt wrote:

> And Happy Thanksgiving to you, grouchy old fart living somewhere south
> of the equator where no one celebrates Thanksgiving :)

It's as much to do with longitude as latitude. It's only in your little
corner of the globe where turkeys are slaughtered en masse a month
early :P


-- 
Neil Bothwick

Profanity, The Language of Computer Professionals.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Re: emerging squid indefinitely

[waltdnes]

On Thu, Nov 26, 2015 at 09:48:37AM +0000, Peter Humphrey wrote
> On Wednesday 25 November 2015 16:03:57 walt wrote:
> 
> > And Happy Thanksgiving to you, grouchy old fart living somewhere south
> > of the equator where no one celebrates Thanksgiving :)
> 
> If I'm not mistaken, Thanksgiving is a purely US occasion  :)

  And in Canada on the 2nd Monday of October.  Although they may have
different names, there are lots of equivalant celebrations around the
planet.  http://www.theholidayspot.com/thanksgiving/around_the_world/
lists several of them.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Re: emerging squid indefinitely

[J. Roeleveld]

On 26 November 2015 12:22:45 CET, waltdnes@waltdnes.org wrote:
>On Thu, Nov 26, 2015 at 09:48:37AM +0000, Peter Humphrey wrote
>> On Wednesday 25 November 2015 16:03:57 walt wrote:
>> 
>> > And Happy Thanksgiving to you, grouchy old fart living somewhere
>south
>> > of the equator where no one celebrates Thanksgiving :)
>> 
>> If I'm not mistaken, Thanksgiving is a purely US occasion  :)
>
>  And in Canada on the 2nd Monday of October.  Although they may have
>different names, there are lots of equivalant celebrations around the
>planet.  http://www.theholidayspot.com/thanksgiving/around_the_world/
>lists several of them.

Turkeys are safe in the Netherlands....

Can't say the same for some other animals though.... :)
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.