GeorgeNmp
Member
AS64512
- Joined:
- May 2024
- Posts:
- 218
- From:
- Ashburn, US
Failed to load configuration: Invalid argument
The error "Failed to load configuration: Invalid argument" typically indicates a malformed unit file rather than a missing file. The "Unable to locate unit" message often follows when systemd cannot parse what it found.
Please check the following:
- Run `systemd-analyze verify /etc/systemd/system/myapp.service`
- Check for a Byte Order Mark (BOM) at the start of the file: `file /etc/systemd/system/myapp.service`
- Verify line endings with `cat -A` — you may find CRLF sequences (^M$) from a Windows transfer
The [Install] section requires WantedBy= or RequiredBy=. A common template error is omitting the target or using an invalid dependency name.
Also check if Contabo's template mounts /etc/systemd/system as a symlink to an overlay that does not propagate writes correctly. I have observed this behavior with providers using read-only base images and writable overlays on older kernels.
iBGP, eBGP, don't care, just peer