#!/bin/sh
docker-compose up -d
killall -9 dnsmasq
docker-compose up -d pihole
Unfortunately RunLast seems to be running before container stations is started, even though ive also installed his SortMyQPKG's that has the following order;
daNutz wrote: ↑Sun Jul 25, 2021 7:34 pm
Unfortunately RunLast seems to be running before container stations is started, even though ive also installed his SortMyQPKG's that has the following order;
I don't have access to Container Station so I'm unable to test how and when it starts.
Maybe it takes a while to start and doesn't wait for all containers to be up-and-running before releasing control back to QTS to continue processing QPKGs?
You'll need to do some testing and find a workaround.
daNutz wrote: ↑Sun Jul 25, 2021 7:34 pm
Unfortunately RunLast seems to be running before container stations is started, even though ive also installed his SortMyQPKG's that has the following order;
I don't have access to Container Station so I'm unable to test how and when it starts.
Maybe it takes a while to start and doesn't wait for all containers to be up-and-running before releasing control back to QTS to continue processing QPKGs?
You'll need to do some testing and find a workaround.
Hi, I did do some checks and noticed that RunLast was executing before container station, even though in the QPKG order it is set to be near the end (as per above). not sure how i can diagnose why its being started sooner than it should?
daNutz wrote: ↑Mon Jul 26, 2021 7:16 pm
Hi, I did do some checks and noticed that RunLast was executing before container station, even though in the QPKG order it is set to be near the end (as per above). not sure how i can diagnose why its being started sooner than it should?
Hard-to-say. You may need to hack the QPKG service-script files and insert your own tracking logger (example: something that appends the current NAS uptime to a text file would do) to work out when Container Station initially starts, then as it's loading its containers, then again when it exits, and compare this against the start times for RunLast. It's a pain, but it should help you discover when it starts compared to your other QPKGs.
The "theory" RunLast (and SortMyQPKGs) work-on is that QPKGs are started in the order they appear in [/etc/config/qpkg.conf] but I found at-least one exception to that some time back (read the OP here for more info).
daNutz wrote: ↑Mon Jul 26, 2021 7:16 pm
Hi, I did do some checks and noticed that RunLast was executing before container station, even though in the QPKG order it is set to be near the end (as per above). not sure how i can diagnose why its being started sooner than it should?
Hard-to-say. You may need to hack the QPKG service-script files and insert your own tracking logger (example: something that appends the current NAS uptime to a text file would do) to work out when Container Station initially starts, then as it's loading its containers, then again when it exits, and compare this against the start times for RunLast. It's a pain, but it should help you discover when it starts compared to your other QPKGs.
The "theory" RunLast (and SortMyQPKGs) work-on is that QPKGs are started in the order they appear in [/etc/config/qpkg.conf] but I found at-least one exception to that some time back (read the OP here for more info).
Unforutenty im not that intelligent, i tried it on my second nas and had the same issue
This is what the log says, which is why im assuming container station hasn't started;