Blog

Twenty Third Of The Fourth Of Twenty Seventeen

Sugar and starchy foods like rice and potatoes have a draconian status. I wanted to try to live without them and see if they helps in weight loss.

Sugar-free tea didn’t really bother me. The amount of milk I add to my tea already brings some of its natural sugar flavor that I can live with. I would love to get rid of my dependence on added sugar.

Indian diet is so starch rich that it is hard to avoid it. I am going to avoid them intentionally but take it when I have to.

What would be a stoics diet be?

Twenty Second Of The Fourth Of The Twenty Seventeen

The month of April has been interesting for me. I thought my productivity would be at all time high because I would not be traveling the whole month but exactly opposite has happened.

The first couple of days of April were wasted because banks forced me to get out of my home during random times.

The next couple of days were glorious because I had an amazing opportunity to attend the very first Google certification summit.

The rest of the days I was just lazy and tired. My energy levels are low. I am not sure if it’s the heat, food, or extra work I have been doing lately.

I want to try giving up on sugar from tomorrow to control the out of hand weight gain I have been experiencing lately.

How To Investigate Failed To Start Load Kernel Modules Error?

Failed to start Load Kernel Modules was a constant occurring during my system boot. I finally sat down and decided to investigate it.

The very first task is figure out which modules are causing the problem. For that we need the PID of process where modules fail.

[sudhir@workstation ~]$ sudo systemctl restart systemd-modules-load.service 
[sudo] password for sudhir: 
Job for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.
[sudhir@workstation ~]$ systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-02-23 21:36:05 IST; 12s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 29552 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 29552 (code=exited, status=1/FAILURE)

Feb 23 21:36:05 workstation systemd[1]: Starting Load Kernel Modules...
Feb 23 21:36:05 workstation systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 21:36:05 workstation systemd[1]: Failed to start Load Kernel Modules.
Feb 23 21:36:05 workstation systemd[1]: systemd-modules-load.service: Unit entered failed state.
Feb 23 21:36:05 workstation systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

The important line here is Main PID: 29552 (code=exited, status=1/FAILURE). We have the PID and now we can check journalctl for the faulty modules.

[sudhir@workstation ~]$ journalctl -b _PID=29552
-- Logs begin at Wed 2017-01-04 04:12:18 IST, end at Thu 2017-02-23 21:36:56 IST. --
Feb 23 21:36:05 workstation systemd-modules-load[29552]: Failed to find module 'vboxdrv'
Feb 23 21:36:05 workstation systemd-modules-load[29552]: Failed to find module 'vboxnetflt'
Feb 23 21:36:05 workstation systemd-modules-load[29552]: Failed to find module 'vboxnetadp'
Feb 23 21:36:05 workstation systemd-modules-load[29552]: Failed to find module 'vboxpci'

Now it became clear that the VirtualBox drivers are at fault. This is how you can investigate future system module failures.