Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
udev-trigger failed after udev-init-scripts-28 update
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
yzg
Guru
Guru


Joined: 18 Jun 2005
Posts: 463

PostPosted: Wed Jun 10, 2015 1:15 am    Post subject: udev-trigger failed after udev-init-scripts-28 update Reply with quote

After sys-fs/udev-init-scripts-28 update, udev-trigger fails to start during the boot.

When I tried to start it, I got the message
Code:

# /etc/init.d/udev-trigger start
 * Generating a rule to create a /dev/root symlink ...                                                           [ ok ]
 * Populating /dev with existing devices through uevents ...                                                     [ ok ]
 * ERROR: udev-trigger failed to start


There is an entry in the log file.
Code:

Jun 10 09:22:45 [/etc/init.d/udev-trigger] ERROR: udev-trigger failed to start
Jun 10 09:22:45 [/etc/init.d/net.eth0] net.eth0: not allowed to be hotplugged


Any ideas?


Last edited by yzg on Thu Jun 11, 2015 6:27 am; edited 2 times in total
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 2938
Location: Illinois, USA

PostPosted: Wed Jun 10, 2015 1:17 am    Post subject: Reply with quote

Did you read the news item?
Back to top
View user's profile Send private message
yzg
Guru
Guru


Joined: 18 Jun 2005
Posts: 463

PostPosted: Wed Jun 10, 2015 1:31 am    Post subject: Reply with quote

Yes, udev and udev-trigger were added to sys-init run level. My problem
is the new udev-trigger does not start. I did not change the config.d files.

Code:

2015-06-08-udev-init-scripts-changes
  Title                     udev-init-scripts-28 important changes
  Author                    William Hubbs <williamh@gentoo.org>
  Posted                    2015-06-08
  Revision                  1

In udev-init-scripts-28 and newer, the udev service script has been
split into udev, udev-settle and udev-trigger.

This means the settings in /etc/conf.d/udev have also been migrated
to the appropriate /etc/conf.d files, so be careful when you update your
configuration settings.

udev and udev-trigger will be added to your sysinit runlevel, but not
udev-settle. udev-settle should not be added to a runlevel. Instead, if
a service needs this, it should add "need udev-settle" to its
dependencies.
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7001

PostPosted: Wed Jun 10, 2015 2:08 am    Post subject: Reply with quote

Try --debug --verbose start
You might figure out what is going on better
Back to top
View user's profile Send private message
prffzc
Tux's lil' helper
Tux's lil' helper


Joined: 22 Sep 2005
Posts: 105

PostPosted: Wed Jun 10, 2015 5:46 am    Post subject: Reply with quote

Did you solved this?
Back to top
View user's profile Send private message
phantom4
n00b
n00b


Joined: 25 Oct 2004
Posts: 10
Location: Dresden

PostPosted: Wed Jun 10, 2015 6:04 am    Post subject: Reply with quote

/etc/init.d/udev-trigger --verbose start
* Generating a rule to create a /dev/root symlink ...
* Populating /dev with existing devices through uevents ...
* $:-no} is not set properly
* ERROR: udev-trigger failed to start
Back to top
View user's profile Send private message
phantom4
n00b
n00b


Joined: 25 Oct 2004
Posts: 10
Location: Dresden

PostPosted: Wed Jun 10, 2015 6:36 am    Post subject: Reply with quote

https://bugs.gentoo.org/show_bug.cgi?id=551644
Back to top
View user's profile Send private message
prffzc
Tux's lil' helper
Tux's lil' helper


Joined: 22 Sep 2005
Posts: 105

PostPosted: Wed Jun 10, 2015 11:08 am    Post subject: Reply with quote

For all newbies:
considering you still have X and a writeable system: get an external keyboard.
Re-emerge udev-init-scripts with the PATCH from the bug.
reboot

The message will still be there but the system will work.
Back to top
View user's profile Send private message
derk
Guru
Guru


Joined: 10 Mar 2003
Posts: 347
Location: St Thomas Ontario

PostPosted: Wed Jun 10, 2015 11:31 am    Post subject: Reply with quote

or alternatively (as root)

patch the script directly ..


copy patch to /etc/init.d/

then do:

patch <udev-init-scripts-28-udev-trigger_init_script_fix.patch

delete the patch from /etc/init.d

rm -i udev-init-scripts-28-udev-trigger_init_script_fix.patch


restart service

/etc/init.d/udev-trigger restart

where-upon you discover it still does not work ..

first patch is not a complete fix .. at the moment.. for me

second patch has the fix but missapplies


ah .. figured it out .. the first fix was already applied .. the second patch has the essential item in it

did manual edit of swapping words .. line .. with .. 'contiune' to 'true' ... restart and it works .. YMMV .. seems first fix is applied in tree already .. so second patch : udev-trigger.patch missapplies .. ..
Back to top
View user's profile Send private message
bstaletic
Apprentice
Apprentice


Joined: 05 Apr 2014
Posts: 225

PostPosted: Wed Jun 10, 2015 1:41 pm    Post subject: Reply with quote

Manually changing "continue" to "true" worked.
Back to top
View user's profile Send private message
bstaletic
Apprentice
Apprentice


Joined: 05 Apr 2014
Posts: 225

PostPosted: Wed Jun 10, 2015 1:46 pm    Post subject: Reply with quote

Manually changing "continue" to "true" worked.
Back to top
View user's profile Send private message
derk
Guru
Guru


Joined: 10 Mar 2003
Posts: 347
Location: St Thomas Ontario

PostPosted: Wed Jun 10, 2015 1:57 pm    Post subject: Reply with quote

so we got it to start .. whether .. it really works properly is a different issue .. see bug 551644 comments
Back to top
View user's profile Send private message
pneula
n00b
n00b


Joined: 16 Jan 2009
Posts: 37

PostPosted: Wed Jun 10, 2015 5:13 pm    Post subject: Reply with quote

Strangely, I get my keyboard working using recovery boot mode just by stopping udev and trying to start udev-trigger.

Udev starts but udev-trigger does not, but still when I continue the boot I get X with a working keyboard.

This works without patching.
Back to top
View user's profile Send private message
derk
Guru
Guru


Joined: 10 Mar 2003
Posts: 347
Location: St Thomas Ontario

PostPosted: Wed Jun 10, 2015 6:10 pm    Post subject: Reply with quote

the "true' 'continue' swap just masks the problem .. evidently .. better fix(s) .. see bug 551644 .. final solution not yet resolved
Back to top
View user's profile Send private message
yzg
Guru
Guru


Joined: 18 Jun 2005
Posts: 463

PostPosted: Thu Jun 11, 2015 3:53 am    Post subject: Reply with quote

It is starting with no errors after changing continue to true.
Back to top
View user's profile Send private message
yzg
Guru
Guru


Joined: 18 Jun 2005
Posts: 463

PostPosted: Thu Jun 11, 2015 6:31 am    Post subject: Reply with quote

After updating udev-init-scripts-29, the machine could not start X and could not find Ethernet device. All the tricks which worked with 28 did not work.

I had to downgrade to version 27.
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 774

PostPosted: Thu Jun 11, 2015 6:35 am    Post subject: Reply with quote

yzg, did you do 'etc-update' ?'
Back to top
View user's profile Send private message
yzg
Guru
Guru


Joined: 18 Jun 2005
Posts: 463

PostPosted: Thu Jun 11, 2015 9:49 am    Post subject: Reply with quote

There is no /etc files update after the emerge.
Code:

# etc-update
Scanning Configuration files...
Exiting: Nothing left to do; exiting. :)
Back to top
View user's profile Send private message
Irre
Guru
Guru


Joined: 09 Nov 2013
Posts: 337
Location: Stockholm

PostPosted: Thu Jun 11, 2015 10:12 am    Post subject: Reply with quote

yzg wrote:
After updating udev-init-scripts-29, the machine could not start X and could not find Ethernet device. All the tricks which worked with 28 did not work.

I had to downgrade to version 27.

I had similar problems. I started X, but mouse and keyboard did not work. After some minutes the mouse appeared! So I could leave X. I then:
rc-config restart udev
rc-config restart udev-trigger
After that X works!
But after reboot -- not :?
Back to top
View user's profile Send private message
idoerg
n00b
n00b


Joined: 22 Jan 2012
Posts: 41

PostPosted: Thu Jun 11, 2015 3:42 pm    Post subject: Reply with quote

Hi,

Seems like v29 is still not working smoothly. After boot I don't get X started. I need to get to a virtual console and run:

Code:
/etc/init.d/udev-trigger --verbose restart


And after that restart xdm to get my KDE desktop
Back to top
View user's profile Send private message
yzg
Guru
Guru


Joined: 18 Jun 2005
Posts: 463

PostPosted: Fri Jun 12, 2015 2:42 am    Post subject: Reply with quote

Can the maintainer revert to version 27 until there is a proper fix?
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5302

PostPosted: Fri Jun 12, 2015 4:33 am    Post subject: Reply with quote

I think I've encounter a similar issue that causes all my mounts no to mount.

for the time being, the easiest workaround that doesn't needs patches and stuff is to press Shift + i when the services start (before udev is started and assuming one has interactive boots), start all the services one by one until eaching udev, start udev, wait a few sec and then start udev-trigger.
wait a bit and verify that kms is up and then continue the boot.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
Zagloj
Guru
Guru


Joined: 17 Jun 2005
Posts: 344

PostPosted: Fri Jun 12, 2015 10:28 am    Post subject: Reply with quote

I had an issue with my splash theme at loading screen (error 256), reverted to init-scripts 27 and solved ;)
_________________
Your ideology seems to be: "I hate the fanatics, we shoud kill them all" juantxorena dixit.
Back to top
View user's profile Send private message
steveL
Watchman
Watchman


Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

PostPosted: Fri Jun 12, 2015 3:25 pm    Post subject: Reply with quote

DaggyStyle wrote:
for the time being, the easiest workaround that doesn't needs patches and stuff is to press Shift + i when the services start (before udev is started and assuming one has interactive boots), start all the services one by one until eaching udev, start udev, wait a few sec and then start udev-trigger.
wait a bit and verify that kms is up and then continue the boot.

That's a long-winded way to do a sleep, as per the comments in the bug, though moving the service to boot instead of sysinit may be an option:
Thomas D. wrote:
Well, moving udev-trigger to default run level works for me, too.

But if I add "sleep 10" before

> ebegin "Populating /dev with existing devices through uevents"
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --verbose --type=devices --action=add

udev-trigger will work for me in sysinit like designed. Race condition?


Also interesting to note: This only happens with udev-220-r1 (same with the currently masked udev-220-r2 from tree from "Fri, 12 Jun 2015 13:45:01 +0000").

udev-init-scripts-29 with udev-219 works fine.

Are other people experiencing issues on udev-220 as well?

I say boot as it should be delayed by comparison to running in sysinit, and it's always run; the other option is to add to default and nonetwork.

Though if it's a bug in a particular version of udev, all that would be a distraction. In that case I'd advise the admin to mask the buggy version instead, or to switch to eudev, since separate-udev-without-systemd is a distraction the upstream have given us "wake-up calls" about in the past.

The initial bug,
Code:
${udev_monitor}:-no}
is quite embarrassing, as it implies whoever committed it, both didn't spot it (howling to a shell-scripter) and worse, hadn't even tested it in the most minimal way conceivable.
Back to top
View user's profile Send private message
balkira
Tux's lil' helper
Tux's lil' helper


Joined: 25 Dec 2004
Posts: 116
Location: /local/pub

PostPosted: Wed Jun 17, 2015 1:54 pm    Post subject: Reply with quote

I had the same issue last week. Upgraded to then latest udev-220ish, rebooted and lost network driver+X11 mouse/kbd, combo in my face!! (hopefully I got an arch to dual boot and chroot from).

Then found the b.g.o report and tried to apply the recommended patch.

Oh boy, I shouldn't have read that patch, it still wakes me up at night all sweaty, screaming "closing bracket bash syntax typo, f*ck nooooooo" then falling into a while loop from which I can't break out..

Joke aside, I know and accept that gentoo QA is the worst shame and failure (mm sourcemage might get the trophee) of the whole linux packaging ecosystem (and this for so many years, actually forever) but pushing untested changes (it had to be untested, no way that code would have run, no f*cking way) is plain wrong. It's even worst than that: it looks like me when I started gentoo...

So, after having lost total trust in the udev maintenance team and not using systemd on gentoo, I figured it was time for trying sys-fs/eudev. I got a lot of positive feedback on #gentoo too from users.

I simply unmerged udev and emerge eudev, rebooted and it all worked again. eudev is a fork of udev, without all the systemd stuff.

=> So if you're fed up with udev gentoo brainfarts and you're not using systemd, try out eudev, it just works.
_________________
no way to happiness, happiness is the way
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum