# Failed to start asl3-boot-oneshot.service - ASL3 OneBoot Task **URL:** \ **Category:** AllStarLink\ **Tags:** asl3\ **Created:** [May 1, 2025, 9:54pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210 "2025-05-01T21:54:15Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Rob\_C](https://community.allstarlink.org/user_avatar/community.allstarlink.org/rob_c/32/4029_2.png) [@Rob\_C](https://community.allstarlink.org/u/Rob_C)\ **Post date:** [May 1, 2025, 9:54pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/1 "2025-05-01T21:54:15Z")
I recently updated my ASL3 running on an x86 PC in a cloud server and after the reboot I get an error that a services wont start. Failed to start asl3-boot-oneshot.service - ASL3 OneBoot Task. Any ideas? google has never seen the service. ---
**Author:** ![Chuck](https://community.allstarlink.org/user_avatar/community.allstarlink.org/chuck/32/3682_2.png) [@Chuck](https://community.allstarlink.org/u/Chuck)\ **Post date:** [May 1, 2025, 10:43pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/2 "2025-05-01T22:43:00Z")
It sounds like OneBoot is a service from your cloud provider that is normally invisible to users. Have you checked with their support? It's not part of ASL3 AFAIK. EDIT: I sit corrected; see below. ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [May 1, 2025, 11:57pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/3 "2025-05-01T23:57:08Z")
As @Chuck said this is not part of a norm. Can you post a little more info as to the VPS service provider etc. That is something to dig deeper on. Some VPS's don't have a standard OS kernel, but a proprietary one. Just leads to check.. ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [May 2, 2025, 12:42am UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/4 "2025-05-02T00:42:15Z")
The `asl3-boot-oneshot.service` is part of the "asl3" package. It runs one time at boot, after the network is up, and execs `/usr/bin/asl3-boot-oneshot`. At present, `/usr/bin/asl3-boot-oneshot` is just performing some cleanup to undo some commands that were exec'd early in the year when we were having the kernel / USB issues. Q? what does your system report when you exec : ```auto systemctl status asl3-boot-oneshot.service ``` ---
**Author:** ![Rob\_C](https://community.allstarlink.org/user_avatar/community.allstarlink.org/rob_c/32/4029_2.png) [@Rob\_C](https://community.allstarlink.org/u/Rob_C)\ **Post date:** [May 2, 2025, 6:09am UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/5 "2025-05-02T06:09:31Z")
Everything seems to be working, i just like to know what errors are before there are a problem systemctl status asl3-boot-oneshot.service asl3-boot-oneshot.service - ASL3 OneBoot Task Loaded: loaded (/lib/systemd/system/asl3-boot-oneshot.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2025-05-01 15:35:55 CST; 4h 21min ago Process: 2543 ExecStart=/usr/bin/asl3-boot-oneshot (code=exited, status=100) Main PID: 2543 (code=exited, status=100) CPU: 289ms ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [May 2, 2025, 2:03pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/6 "2025-05-02T14:03:29Z")
> [@Rob\_C](#): > > Everything seems to be working, i just like to know what errors are before there are a problem Odd. There's really not much to `asl3-boot-oneshot`. We only exec 2 commands in the script. The following commands can be used to check that they are available on your system : ```auto which fuser which apt-mark ``` And, as @Mike asked, can you tell us a little bit more about your "x86 PC in a cloud server"? What VPS are you using? Did you install the latest Debian? or some other OS? ---
**Author:** ![Rob\_C](https://community.allstarlink.org/user_avatar/community.allstarlink.org/rob_c/32/4029_2.png) [@Rob\_C](https://community.allstarlink.org/u/Rob_C)\ **Post date:** [May 2, 2025, 3:49pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/7 "2025-05-02T15:49:07Z")
> [@WA3WCO](#): > > ```auto > which fuser > which apt-mark > > ``` /usr/bin/fuser [1]+ Exit 1 Xvfb :99 /usr/bin/apt-mark Nanode 1 GB Linode started with Debian 12 install via linode then a fresh install of ASL3 Supermon, Allscan, DVSwitch ---
**Author:** ![W8ONE](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w8one/32/3856_2.png) [@W8ONE](https://community.allstarlink.org/u/W8ONE)\ **Post date:** [May 3, 2025, 3:48pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/8 "2025-05-03T15:48:02Z")
I have the same thing on a dell wyse 3040 wonka644661@wonka:~$ systemctl status asl3-boot-oneshot.service × asl3-boot-oneshot.service - ASL3 OneBoot Task Loaded: loaded (/lib/systemd/system/asl3-boot-oneshot.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2025-05-03 10:46:57 EDT; 8min ago Process: 573 ExecStart=/usr/bin/asl3-boot-oneshot (code=exited, status=100) Main PID: 573 (code=exited, status=100) CPU: 1.058s Warning: some journal files were not opened due to insufficient permissions. wonka644661@wonka:~$ which fuser /usr/bin/fuser wonka644661@wonka:~$ which apt-mark /usr/bin/apt-mark ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [May 3, 2025, 4:25pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/9 "2025-05-03T16:25:12Z")
Here's the scoop: ```auto $ sudo bash -x /usr/bin/asl3-boot-oneshot wa3wco@wa3wco-asl:~$ sudo bash -x /usr/bin/asl3-boot-oneshot + set -e + fuser /var/lib/dpkg/lock ++ grep -E '^Model' /proc/cpuinfo ++ grep -q 'Raspberry Pi' + apt-mark unhold linux-image-amd64 linux-headers-amd64 linux-image-6.1.0-28-amd64 linux-headers-6.1.0-28-amd64 linux-image-amd64 was already not on hold. linux-headers-amd64 was already not on hold. linux-headers-6.1.0-28-amd64 was already not on hold. E: Unable to locate package linux-image-6.1.0-28-amd64 E: Couldn't find any package by glob 'linux-image-6.1.0-28-amd64' E: Couldn't find any package by regex 'linux-image-6.1.0-28-amd64' ``` What's happening is that the `apt-mark` command is returning an error because the request action was not successful. But, in this case, it's OK if the packages are not installed and/or not marked with a "hold". We just need to ignore the `apt-mark` exit status and add an `exit 0` to end of the script. ... and a fix will be in our "next" set of package updates 🙂 ---
**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\ **Post date:** [May 8, 2025, 4:33pm UTC](https://community.allstarlink.org/t/failed-to-start-asl3-boot-oneshot-service-asl3-oneboot-task/23210/10 "2025-05-08T16:33:30Z")
Closed on May 8, 2025, 4:33pm UTC This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.