Home
PureOS Tracker
Search
Configure Global Search
Log In
Transactions
Slow system startup
Change Details
Change Details
Old
New
Diff
{nav icon=home, name=Main Page > icon=wrench, name=Troubleshooting > Slow system startup} Troubleshoot slow system startup --- == Problem == System takes few minutes to start, but eventually it does get to the graphical user interface. == Check == You can check how much time the system exactly needed to start if you run this command in terminal: {icon terminal}`systemd-analyze` It will output something like this: {F45769, alt=sstd1, size=full} To see how long each of the services took to start, run: {icon terminal}`systemd-analyze blame` which should give: {F45771, alt=sstd2, size=full} Use {key arrow-up} and {key arrow-down} to scroll the output, use {key Q} to quit the command (to exit). To output this into a text file, use: {icon terminal}`systemd-analyze blame > startup.log` which will create //startup.log// text file in your home directory. == Solution == If you see some service took suspiciously longer time to start, you have to search the system logs to see if there is any particular problem. For example, running: {icon terminal}`sudo journalctl -x -b -u NetworkManager-wait-online.service` will list logs just for this service, while running: {icon terminal}`sudo journalctl -x -b` will allow you to examine all logs for the current boot session to see if there is any particular problem causing the slow system start.
{nav icon=home, name=Main Page > icon=wrench, name=Troubleshooting > Slow system startup} Troubleshoot slow system startup --- == Problem == System takes few minutes to start, but eventually it does get to the graphical user interface. == Check == You can check how much time the system exactly needed to start if you run this command in terminal: {icon terminal}`systemd-analyze` It will output something like this: {F45769, alt=sstd1, size=full} To see how long each of the services took to start, run: {icon terminal}`systemd-analyze blame` which should give: {F45771, alt=sstd2, size=full} Use {key arrow-up} and {key arrow-down} to scroll the output, use {key Q} to quit the command (to exit). To output this into a text file, use: {icon terminal}`systemd-analyze blame > startup.log` which will create //startup.log// text file in your home directory. == Solution == If you see some service took suspiciously longer time to start, you have to search the system logs to see if there is any particular problem. For example, running: {icon terminal}`sudo journalctl -x -b -u NetworkManager-wait-online.service` will list logs just for this service, while running: {icon terminal}`sudo journalctl -x -b` will allow you to examine all logs for the current boot session to see if there is any particular problem causing the slow system start.
Continue