[SCW C1] Failed to start Network Name Resolution

This forum is for topics dealing with problems with software specifically in the ARMv7h repo.

[SCW C1] Failed to start Network Name Resolution

Postby Chazy » Tue Aug 02, 2016 9:09 pm

I'm getting the following error when booting up my scaleway c1 server, after a full system upgrade (the image is 2/3 months old I think):

$this->bbcode_second_pass_quote('', '[')FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.
[ OK ] Started SCW generate machine id.
Starting Hostname Service...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[ OK ] Started Hostname Service.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[ OK ] Started SCW fetch ssh keys from metadata.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Started One-Shot Network Time Service.


And I think that is causing my vhosts to not work (apache always shows /srv/http).

Can someone please help me solve this? Thanks.
Chazy
 
Posts: 8
Joined: Tue Aug 02, 2016 8:54 pm

Re: [SCW C1] Failed to start Network Name Resolution

Postby WarheadsSE » Tue Aug 02, 2016 10:40 pm

$this->bbcode_second_pass_code('', 'See 'systemctl status systemd-resolved.service' for details.')
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: [SCW C1] Failed to start Network Name Resolution

Postby Chazy » Wed Aug 03, 2016 12:47 am

Right, sorry.

$this->bbcode_second_pass_quote('', '#') systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/etc/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Tue 2016-08-02 23:39:01 UTC; 1h 5min ago
Docs: man:systemd-resolved.service(8)
Process: 3455 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=1/FAILURE)
Main PID: 3455 (code=exited, status=1/FAILURE)
Status: "Shutting down..."

Aug 02 23:39:01 scw-28a908 systemd[1]: Failed to start Network Name Resolution.
Aug 02 23:39:01 scw-28a908 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 02 23:39:01 scw-28a908 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 02 23:39:01 scw-28a908 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 02 23:39:01 scw-28a908 systemd[1]: Stopped Network Name Resolution.
Aug 02 23:39:01 scw-28a908 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 02 23:39:01 scw-28a908 systemd[1]: Failed to start Network Name Resolution.
Aug 02 23:39:01 scw-28a908 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 02 23:39:01 scw-28a908 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

-- Subject: Unit systemd-resolved.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-resolved.service has begun starting up.
Aug 03 00:50:21 scw-28a908 systemd-resolved[3752]: Failed to increase capabilities: Operation not permitted
Aug 03 00:50:21 scw-28a908 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 03 00:50:21 scw-28a908 systemd[1]: Failed to start Network Name Resolution.
-- Subject: Unit systemd-resolved.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-resolved.service has failed.
--
-- The result is failed.
Aug 03 00:50:21 scw-28a908 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 03 00:50:21 scw-28a908 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 03 00:50:21 scw-28a908 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 03 00:50:21 scw-28a908 systemd[1]: Stopped Network Name Resolution.
-- Subject: Unit systemd-resolved.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-resolved.service has finished shutting down.
Aug 03 00:50:21 scw-28a908 systemd[1]: Starting Network Name Resolution...
-- Subject: Unit systemd-resolved.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-resolved.service has begun starting up.
Aug 03 00:50:21 scw-28a908 systemd-resolved[3756]: Failed to increase capabilities: Operation not permitted
Aug 03 00:50:21 scw-28a908 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 03 00:50:21 scw-28a908 systemd[1]: Failed to start Network Name Resolution.


Any idea why is not working?
Chazy
 
Posts: 8
Joined: Tue Aug 02, 2016 8:54 pm

Re: [SCW C1] Failed to start Network Name Resolution

Postby Chazy » Sat Aug 06, 2016 1:39 pm

I don't care if I have to reinstall again, I just need this working correctly...

Does anyone, please, know what's wrong with that service?

Thanks.
Chazy
 
Posts: 8
Joined: Tue Aug 02, 2016 8:54 pm

Re: [SCW C1] Failed to start Network Name Resolution

Postby WarheadsSE » Sun Aug 07, 2016 2:27 pm

If you can get us a snippet of the actual logs from the journal, that might help
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: [SCW C1] Failed to start Network Name Resolution

Postby Chazy » Sun Aug 07, 2016 2:41 pm

I read that it may be a systemd bug: https://github.com/systemd/systemd/issues/3484

It seems fixed, I'll try the new version once there's stock of the C1 server again... The arch linux image (from scaleway) dates from december last year.
Chazy
 
Posts: 8
Joined: Tue Aug 02, 2016 8:54 pm

Re: [SCW C1] Failed to start Network Name Resolution

Postby WarheadsSE » Sun Aug 07, 2016 10:43 pm

:| Yeah .. I lost mine too trying to re-image :cry:
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: [SCW C1] Failed to start Network Name Resolution

Postby Chazy » Mon Aug 08, 2016 3:20 am

Let's hope they restock soon this week :?
Chazy
 
Posts: 8
Joined: Tue Aug 02, 2016 8:54 pm

Re: [SCW C1] Failed to start Network Name Resolution

Postby Chazy » Sat Aug 13, 2016 12:28 am

No luck, I'm commenting on the issue I linked above.

This is the log:

$this->bbcode_second_pass_quote('', '#') journalctl | grep systemd-resolved
Aug 13 00:19:19 scw-84ea69 systemd-resolved[3174]: Failed to increase capabilities: Operation not permitted
Aug 13 00:19:19 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:19:19 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:19:19 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:19:19 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:19:20 scw-84ea69 systemd-resolved[3262]: Failed to increase capabilities: Operation not permitted
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:19:20 scw-84ea69 systemd-resolved[3271]: Failed to increase capabilities: Operation not permitted
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:19:20 scw-84ea69 systemd-resolved[3274]: Failed to increase capabilities: Operation not permitted
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:19:20 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:19:21 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:19:21 scw-84ea69 systemd-resolved[3277]: Failed to increase capabilities: Operation not permitted
Aug 13 00:19:21 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:19:21 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:19:21 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:19:21 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:19:21 scw-84ea69 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 13 00:19:21 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:19:21 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Aug 13 00:20:11 scw-84ea69 systemd-resolved[3320]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:11 scw-84ea69 systemd-resolved[3324]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:11 scw-84ea69 systemd-resolved[3328]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:11 scw-84ea69 systemd-resolved[3332]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:11 scw-84ea69 systemd-resolved[3338]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:11 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Aug 13 00:20:15 scw-84ea69 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 13 00:20:15 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Aug 13 00:20:25 scw-84ea69 systemd-resolved[3346]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:25 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:25 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:25 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:25 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:25 scw-84ea69 systemd-resolved[3350]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:25 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:25 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:25 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:25 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:26 scw-84ea69 systemd-resolved[3355]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:26 scw-84ea69 systemd-resolved[3359]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:26 scw-84ea69 systemd-resolved[3363]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:26 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Aug 13 00:20:28 scw-84ea69 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 13 00:20:28 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Aug 13 00:20:29 scw-84ea69 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 13 00:20:29 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Aug 13 00:20:34 scw-84ea69 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 13 00:20:34 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Aug 13 00:20:36 scw-84ea69 systemd-resolved[3376]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:36 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:37 scw-84ea69 systemd-resolved[3380]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:37 scw-84ea69 systemd-resolved[3384]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:37 scw-84ea69 systemd-resolved[3388]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:37 scw-84ea69 systemd-resolved[3392]: Failed to increase capabilities: Operation not permitted
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 13 00:20:37 scw-84ea69 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Chazy
 
Posts: 8
Joined: Tue Aug 02, 2016 8:54 pm
Top

Re: [SCW C1] Failed to start Network Name Resolution

Postby WarheadsSE » Sat Aug 13, 2016 1:40 am

Finally managed to get a replacement, and I am seeing something similar from the moment I run `pacman -Syu` and reboot. Researching as I have time.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Next

Return to ARMv7h

Who is online

Users browsing this forum: No registered users and 8 guests