New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure iotedge version 1.0.2 not working #378

Closed
payalgaikwad42 opened this Issue Oct 1, 2018 · 11 comments

Comments

Projects
None yet
4 participants
@payalgaikwad42

payalgaikwad42 commented Oct 1, 2018

Hi,
I am trying do set up of iot-edge on my ubuntu 16.04 machine by following steps in following document :https://docs.microsoft.com/en-us/azure/iot-edge/quickstart-linux#install-and-start-the-iot-edge-runtime

but it is giving me an error that iotedge daemon fails to start.
the logs of $ sudo systemctl status iotedge command are as follows:
● iotedge.service - Azure IoT Edge daemon
Loaded: loaded (/lib/systemd/system/iotedge.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Mon 2018-10-01 15:37:55 IST; 9min ago
Docs: man:iotedged(8)
Process: 12151 ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml (code=exited, status=1/FAILURE)
Main PID: 12151 (code=exited, status=1/FAILURE)

Oct 01 15:37:55 payalG-PC systemd[1]: iotedge.service: Unit entered failed state.
Oct 01 15:37:55 payalG-PC systemd[1]: iotedge.service: Failed with result 'exit-code'.
Oct 01 15:37:55 payalG-PC systemd[1]: iotedge.service: Service hold-off time over, scheduling restart.
Oct 01 15:37:55 payalG-PC systemd[1]: Stopped Azure IoT Edge daemon.
Oct 01 15:37:55 payalG-PC systemd[1]: iotedge.service: Start request repeated too quickly.
Oct 01 15:37:55 payalG-PC systemd[1]: Failed to start Azure IoT Edge daemon.

also i am getting following error after running systemctl restart iotedge command :

Job for iotedge.service failed because the control process exited with error code.

can anybody help me with this?

@myagley

This comment has been minimized.

Contributor

myagley commented Oct 1, 2018

Can you please provide more of the iotedged's logs? You can find out more information about obtaining the logs here: https://docs.microsoft.com/en-us/azure/iot-edge/troubleshoot#check-the-status-of-the-iot-edge-security-manager-and-its-logs

@payalgaikwad42

This comment has been minimized.

payalgaikwad42 commented Oct 3, 2018

following are the logs of journalctl -u iotedge --no-pager --no-full

  • Logs begin at Wed 2018-10-03 09:45:13 IST, end at Wed 2018-10-03 09:47:22 IST. --
Oct 03 09:45:39 payalG-PC systemd[1]: Started Azure IoT Edge daemon.
Oct 03 09:45:40 payalG-PC iotedged[2039]: 2018-10-03T04:15:40Z [INFO] - Starting Azure IoT Edge Security Daemon
Oct 03 09:45:40 payalG-PC iotedged[2039]: 2018-10-03T04:15:40Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738)
Oct 03 09:45:40 payalG-PC iotedged[2039]: 2018-10-03T04:15:40Z [INFO] - Using config file: /etc/iotedge/config.yaml
Oct 03 09:45:40 payalG-PC iotedged[2039]: 2018-10-03T04:15:40Z [INFO] - Using runtime network id azure-iot-edge
Oct 03 09:45:40 payalG-PC iotedged[2039]: 2018-10-03T04:15:40Z [INFO] - Initializing the module runtime...
Oct 03 09:45:50 payalG-PC iotedged[2039]: 2018-10-03T04:15:50Z [INFO] - Finished initializing the module runtime.
Oct 03 09:45:50 payalG-PC iotedged[2039]: 2018-10-03T04:15:50Z [INFO] - Configuring /var/lib/iotedge as the home directory.
Oct 03 09:45:50 payalG-PC iotedged[2039]: 2018-10-03T04:15:50Z [INFO] - Configuring certificates...
Oct 03 09:45:50 payalG-PC iotedged[2039]: 2018-10-03T04:15:50Z [INFO] - Transparent gateway certificates not found, operating in quick start mode...
Oct 03 09:45:50 payalG-PC iotedged[2039]: 2018-10-03T04:15:50Z [INFO] - Finished configuring certificates.
Oct 03 09:45:50 payalG-PC iotedged[2039]: 2018-10-03T04:15:50Z [INFO] - Initializing hsm...
Oct 03 09:45:50 payalG-PC systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE
Oct 03 09:45:50 payalG-PC systemd[1]: iotedge.service: Unit entered failed state.
Oct 03 09:45:50 payalG-PC systemd[1]: iotedge.service: Failed with result 'exit-code'.
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Service hold-off time over, scheduling restart.
Oct 03 09:45:51 payalG-PC systemd[1]: Stopped Azure IoT Edge daemon.
Oct 03 09:45:51 payalG-PC systemd[1]: Started Azure IoT Edge daemon.
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Starting Azure IoT Edge Security Daemon
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738)
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Using config file: /etc/iotedge/config.yaml
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Using runtime network id azure-iot-edge
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Initializing the module runtime...
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Finished initializing the module runtime.
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Configuring /var/lib/iotedge as the home directory.
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Configuring certificates...
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Transparent gateway certificates not found, operating in quick start mode...
Oct 03 09:45:51 payalG-PC iotedged[3656]: 2018-10-03T04:15:51Z [INFO] - Finished configuring certificates.
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Unit entered failed state.
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Failed with result 'exit-code'.
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Service hold-off time over, scheduling restart.
Oct 03 09:45:51 payalG-PC systemd[1]: Stopped Azure IoT Edge daemon.
Oct 03 09:45:51 payalG-PC systemd[1]: Started Azure IoT Edge daemon.
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Starting Azure IoT Edge Security Daemon
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738)
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Using config file: /etc/iotedge/config.yaml
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Using runtime network id azure-iot-edge
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Initializing the module runtime...
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Finished initializing the module runtime.
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Configuring /var/lib/iotedge as the home directory.
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Configuring certificates...
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Transparent gateway certificates not found, operating in quick start mode...
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Finished configuring certificates.
Oct 03 09:45:51 payalG-PC iotedged[3679]: 2018-10-03T04:15:51Z [INFO] - Initializing hsm...
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Unit entered failed state.
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Failed with result 'exit-code'.
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Service hold-off time over, scheduling restart.
Oct 03 09:45:51 payalG-PC systemd[1]: Stopped Azure IoT Edge daemon.
Oct 03 09:45:51 payalG-PC systemd[1]: Started Azure IoT Edge daemon.
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Starting Azure IoT Edge Security Daemon
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738)
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Using config file: /etc/iotedge/config.yaml
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Using runtime network id azure-iot-edge
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Initializing the module runtime...
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Finished initializing the module runtime.
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Configuring /var/lib/iotedge as the home directory.
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Configuring certificates...
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Transparent gateway certificates not found, operating in quick start mode...
Oct 03 09:45:51 payalG-PC iotedged[3705]: 2018-10-03T04:15:51Z [INFO] - Finished configuring certificates.
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Unit entered failed state.
Oct 03 09:45:51 payalG-PC systemd[1]: iotedge.service: Failed with result 'exit-code'.
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Service hold-off time over, scheduling restart.
Oct 03 09:45:54 payalG-PC systemd[1]: Stopped Azure IoT Edge daemon.
Oct 03 09:45:54 payalG-PC systemd[1]: Started Azure IoT Edge daemon.
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Starting Azure IoT Edge Security Daemon
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738)
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Using config file: /etc/iotedge/config.yaml
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Using runtime network id azure-iot-edge
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Initializing the module runtime...
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Finished initializing the module runtime.
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Configuring /var/lib/iotedge as the home directory.
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Configuring certificates...
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Transparent gateway certificates not found, operating in quick start mode...
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Finished configuring certificates.
Oct 03 09:45:54 payalG-PC iotedged[3734]: 2018-10-03T04:15:54Z [INFO] - Initializing hsm...
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Unit entered failed state.
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Failed with result 'exit-code'.
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Service hold-off time over, scheduling restart.
Oct 03 09:45:54 payalG-PC systemd[1]: Stopped Azure IoT Edge daemon.
Oct 03 09:45:54 payalG-PC systemd[1]: Started Azure IoT Edge daemon.
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Starting Azure IoT Edge Security Daemon
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Version - 1.0.2 (f6fcdb2e24ac2af977e748e9f2b8a37245b92738)
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Using config file: /etc/iotedge/config.yaml
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Using runtime network id azure-iot-edge
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Initializing the module runtime...
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Finished initializing the module runtime.
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Configuring /var/lib/iotedge as the home directory.
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Configuring certificates...
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Transparent gateway certificates not found, operating in quick start mode...
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Finished configuring certificates.
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Main process exited, code=exited, status=1/FAILURE
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Unit entered failed state.
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Failed with result 'exit-code'.
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Service hold-off time over, scheduling restart.
Oct 03 09:45:54 payalG-PC systemd[1]: Stopped Azure IoT Edge daemon.
Oct 03 09:45:54 payalG-PC systemd[1]: iotedge.service: Start request repeated too quickly.
Oct 03 09:45:54 payalG-PC systemd[1]: Failed to start Azure IoT Edge daemon.

I have tried to re-installing everything from scratch but it is still not working.

@payalgaikwad42

This comment has been minimized.

payalgaikwad42 commented Oct 3, 2018

payal@payalG-PC:~$ journalctl -xe
Oct 03 10:16:09 payalG-PC systemd[1]: iotedge.socket: Unit entered failed state.
Oct 03 10:16:09 payalG-PC systemd[1]: iotedge.mgmt.socket: Unit entered failed state.
Oct 03 10:16:11 payalG-PC sudo[11452]:    payal : TTY=pts/18 ; PWD=/home/payal ; USER=root ; COMMAND=/bin/systemctl restart iotedge
Oct 03 10:16:11 payalG-PC sudo[11452]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 03 10:16:11 payalG-PC systemd[1]: Stopped Azure IoT Edge daemon.
-- Subject: Unit iotedge.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit iotedge.service has finished shutting down.
Oct 03 10:16:11 payalG-PC systemd[1]: Starting Azure IoT Edge daemon management socket.
-- Subject: Unit iotedge.mgmt.socket has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit iotedge.mgmt.socket has begun starting up.
Oct 03 10:16:11 payalG-PC systemd[1]: Starting Azure IoT Edge daemon workload socket.
-- Subject: Unit iotedge.socket has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit iotedge.socket has begun starting up.
Oct 03 10:16:11 payalG-PC systemd[1]: Listening on Azure IoT Edge daemon management socket.
-- Subject: Unit iotedge.mgmt.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit iotedge.mgmt.socket has finished starting up.
-- 
-- The start-up result is done.
Oct 03 10:16:11 payalG-PC systemd[1]: Listening on Azure IoT Edge daemon workload socket.
-- Subject: Unit iotedge.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit iotedge.socket has finished starting up.
-- 
-- The start-up result is done.
Oct 03 10:16:11 payalG-PC systemd[1]: iotedge.service: Start request repeated too quickly.
Oct 03 10:16:11 payalG-PC systemd[1]: Failed to start Azure IoT Edge daemon.
-- Subject: Unit iotedge.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit iotedge.service has failed.
-- 
-- The result is failed.
Oct 03 10:16:11 payalG-PC systemd[1]: iotedge.socket: Unit entered failed state.
Oct 03 10:16:11 payalG-PC systemd[1]: iotedge.mgmt.socket: Unit entered failed state.
Oct 03 10:16:11 payalG-PC sudo[11452]: pam_unix(sudo:session): session closed for user root
lines 1583-1632/1632 (END)

ADDITIONAL INFORMATION

payal@payalG-PC:~$ cat /lib/systemd/system/iotedge.service
[Unit]
Description=Azure IoT Edge daemon
After=network-online.target iotedge.socket iotedge.mgmt.socket
Requires=network-online.target iotedge.socket iotedge.mgmt.socket
Documentation=man:iotedged(8)

[Service]
ExecStart=/usr/bin/iotedged -c /etc/iotedge/config.yaml
KillMode=process
TimeoutStartSec=600
TimeoutStopSec=40
Restart=on-failure
User=iotedge
Group=iotedge

[Install]
WantedBy=multi-user.target
Also=iotedge.socket iotedge.mgmt.socket
@payalgaikwad42

This comment has been minimized.

payalgaikwad42 commented Oct 3, 2018

on running "iotedge list" command i am getting following error:
An error in the management http client occurred.
caused by: Hyper error
caused by: Connection refused (os error 111)

and when i check in the azure portal all the modules are in running state here is the screenshot:
azure

@myagley

This comment has been minimized.

Contributor

myagley commented Oct 3, 2018

Due to a bug in systemd/journald the last couple of log lines are truncated when a program exits. Is it possible to get the logs without specifying the -u iotedge when the failure happens?

journalctl --no-pager --no-full

The next step in the startup sequence is to initialize the HSM library, which is where I suspect the issue is. The important bit of information is after the following logs:

Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Configuring certificates...
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Transparent gateway certificates not found, operating in quick start mode...
Oct 03 09:45:54 payalG-PC iotedged[3759]: 2018-10-03T04:15:54Z [INFO] - Finished configuring certificates.
@payalgaikwad42

This comment has been minimized.

payalgaikwad42 commented Oct 4, 2018

Thank you for the information,
Yes it is possible to get the logs without -u iotedge
journalctl --no-pager --no-full:
Oct 04 09:58:01 payalG-PC CRON[4042]: pam_unix(cron:session): session closed for user payal
Oct 04 09:58:39 payalG-PC anacron[1058]: Job cron.daily' started Oct 04 09:58:39 payalG-PC anacron[4056]: Updated timestamp for job cron.daily' to 2018-10-04
Oct 04 09:58:40 payalG-PC cracklib[4084]: no dictionary update necessary.
Oct 04 09:58:41 payalG-PC systemd[1]: Stopping Make remote CUPS printers available locally...
Oct 04 09:58:41 payalG-PC systemd[1]: Stopped Make remote CUPS printers available locally.
Oct 04 09:58:41 payalG-PC systemd[1]: Stopping CUPS Scheduler...
Oct 04 09:58:41 payalG-PC systemd[1]: Stopped CUPS Scheduler.
Oct 04 09:58:41 payalG-PC systemd[1]: Stopped CUPS Scheduler.
Oct 04 09:58:41 payalG-PC systemd[1]: Stopping CUPS Scheduler.
Oct 04 09:58:41 payalG-PC systemd[1]: Started CUPS Scheduler.
Oct 04 09:58:41 payalG-PC systemd[1]: Started CUPS Scheduler.
Oct 04 09:58:41 payalG-PC systemd[1]: Started Make remote CUPS printers available locally.
Oct 04 09:59:01 payalG-PC CRON[4409]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 09:59:01 payalG-PC CRON[4410]: (payal) CMD (./cleanJob.sh)
Oct 04 09:59:01 payalG-PC CRON[4409]: (CRON) info (No MTA installed, discarding output)
Oct 04 09:59:01 payalG-PC CRON[4409]: pam_unix(cron:session): session closed for user payal
Oct 04 09:59:57 payalG-PC anacron[1058]: Job `cron.daily' terminated
Oct 04 09:59:57 payalG-PC anacron[1058]: Normal exit (1 job run)
Oct 04 10:00:01 payalG-PC CRON[4462]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:00:01 payalG-PC CRON[4463]: (payal) CMD (./cleanJob.sh)
Oct 04 10:00:01 payalG-PC CRON[4462]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:00:01 payalG-PC CRON[4462]: pam_unix(cron:session): session closed for user payal
Oct 04 10:01:01 payalG-PC CRON[4466]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:01:01 payalG-PC CRON[4467]: (payal) CMD (./cleanJob.sh)
Oct 04 10:01:01 payalG-PC CRON[4466]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:01:01 payalG-PC CRON[4466]: pam_unix(cron:session): session closed for user payal
Oct 04 10:01:50 payalG-PC rtkit-daemon[1853]: Supervising 2 threads of 1 processes of 1 users.
Oct 04 10:01:50 payalG-PC rtkit-daemon[1853]: Successfully made thread 4472 of process 1852 (n/a) owned by '108' RT at priority 5.
Oct 04 10:01:50 payalG-PC rtkit-daemon[1853]: Supervising 3 threads of 1 processes of 1 users.
Oct 04 10:01:50 payalG-PC lightdm[1801]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=payal
Oct 04 10:01:52 payalG-PC lightdm[4473]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file:...irectory
Oct 04 10:01:52 payalG-PC lightdm[4473]: PAM adding faulty module: pam_kwallet.so
Oct 04 10:01:52 payalG-PC lightdm[4473]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object fil...irectory
Oct 04 10:01:52 payalG-PC lightdm[4473]: PAM adding faulty module: pam_kwallet5.so
Oct 04 10:01:52 payalG-PC lightdm[4473]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "payal"
Oct 04 10:02:01 payalG-PC CRON[4474]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:02:01 payalG-PC CRON[4475]: (payal) CMD (./cleanJob.sh)
Oct 04 10:02:01 payalG-PC CRON[4474]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:02:01 payalG-PC CRON[4474]: pam_unix(cron:session): session closed for user payal
Oct 04 10:02:05 payalG-PC org.gtk.vfs.Daemon[1749]: A connection to the bus can't be made
Oct 04 10:02:05 payalG-PC lightdm[1711]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Oct 04 10:02:05 payalG-PC lightdm[4473]: pam_unix(lightdm:session): session opened for user payal by (uid=0)
Oct 04 10:02:05 payalG-PC systemd[1]: Created slice User Slice of payal.
Oct 04 10:02:05 payalG-PC systemd[1]: Starting User Manager for UID 1000...
Oct 04 10:02:05 payalG-PC systemd-logind[1075]: New session c2 of user payal.
Oct 04 10:02:05 payalG-PC systemd[1]: Started Session c2 of user payal.
Oct 04 10:02:05 payalG-PC systemd[4486]: pam_unix(systemd-user:session): session opened for user payal by (uid=0)
Oct 04 10:02:05 payalG-PC systemd[4486]: Reached target Timers.
Oct 04 10:02:05 payalG-PC systemd[4486]: Reached target Paths.
Oct 04 10:02:05 payalG-PC systemd[4486]: Reached target Sockets.
Oct 04 10:02:05 payalG-PC systemd[4486]: Reached target Basic System.
Oct 04 10:02:05 payalG-PC systemd[4486]: Reached target Default.
Oct 04 10:02:05 payalG-PC systemd[4486]: Startup finished in 12ms.
Oct 04 10:02:05 payalG-PC systemd[1]: Started User Manager for UID 1000.
Oct 04 10:02:07 payalG-PC org.ayatana.bamf[4580]: bamfdaemon start/running, process 4683
Oct 04 10:02:09 payalG-PC org.a11y.atspi.Registry[4726]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct 04 10:02:10 payalG-PC dbus[1034]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Oct 04 10:02:10 payalG-PC rtkit-daemon[1853]: Successfully made thread 4815 of process 4815 (n/a) owned by '1000' high priority at nice level -11.
Oct 04 10:02:10 payalG-PC rtkit-daemon[1853]: Supervising 4 threads of 2 processes of 2 users.
Oct 04 10:02:10 payalG-PC org.gnome.ScreenSaver[4580]: ** (gnome-screensaver:4762): WARNING **: Couldn't get presence status: The name org.gn...e files
Oct 04 10:02:11 payalG-PC gnome-keyring-daemon[4492]: The SSH agent was already initialized
Oct 04 10:02:11 payalG-PC gnome-session[4719]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 04 10:02:11 payalG-PC gnome-keyring-daemon[4492]: The PKCS#11 component was already initialized
Oct 04 10:02:11 payalG-PC gnome-session[4719]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 04 10:02:11 payalG-PC gnome-keyring-daemon[4492]: The Secret Service was already initialized
Oct 04 10:02:11 payalG-PC gnome-session[4719]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Supervising 4 threads of 2 processes of 2 users.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Successfully made thread 4871 of process 4815 (n/a) owned by '1000' RT at priority 5.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Supervising 5 threads of 2 processes of 2 users.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Supervising 5 threads of 2 processes of 2 users.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Successfully made thread 4872 of process 4815 (n/a) owned by '1000' RT at priority 5.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Supervising 6 threads of 2 processes of 2 users.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Successfully made thread 4876 of process 4876 (n/a) owned by '1000' high priority at nice level -11.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Supervising 7 threads of 3 processes of 2 users.
Oct 04 10:02:11 payalG-PC pulseaudio[4876]: [pulseaudio] pid.c: Daemon already running.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Successfully made thread 4880 of process 4880 (n/a) owned by '1000' high priority at nice level -11.
Oct 04 10:02:11 payalG-PC rtkit-daemon[1853]: Supervising 7 threads of 3 processes of 2 users.
Oct 04 10:02:11 payalG-PC pulseaudio[4880]: [pulseaudio] pid.c: Daemon already running.
Oct 04 10:02:11 payalG-PC dbus[1034]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.lo....service'
Oct 04 10:02:11 payalG-PC systemd[1]: Starting Locale Service...
Oct 04 10:02:12 payalG-PC dbus[1034]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct 04 10:02:12 payalG-PC systemd[1]: Started Locale Service.
Oct 04 10:02:12 payalG-PC gnome-session[4719]: (process:4914): indicator-application-service-WARNING **: Unable to get watcher name 'org.kde...Watcher'
Oct 04 10:02:12 payalG-PC gnome-session[4719]: (process:4914): indicator-application-service-WARNING **: Name Lost
Oct 04 10:02:12 payalG-PC polkitd(authority=local)[1428]: Registered Authentication Agent for unix-session:c2 (system bus name :1.83 [/usr/li....UTF-8)
Oct 04 10:02:12 payalG-PC gnome-session-binary[4719]: Entering running state
Oct 04 10:02:13 payalG-PC dbus[1034]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Oct 04 10:02:13 payalG-PC systemd[1]: Starting Disk Manager...
Oct 04 10:02:13 payalG-PC udisksd[4960]: udisks daemon version 2.1.7 starting
Oct 04 10:02:13 payalG-PC dbus[1034]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Oct 04 10:02:13 payalG-PC systemd[1]: Started Disk Manager.
Oct 04 10:02:13 payalG-PC udisksd[4960]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Oct 04 10:02:13 payalG-PC dbus[1034]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service'
Oct 04 10:02:13 payalG-PC systemd[1]: Starting Firmware update daemon...
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Autoprobing TCP port in (all) network interface
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Listening IPv6://[::]:5900
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Listening IPv4://0.0.0.0:5900
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Autoprobing selected port 5900
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Advertising security type: 'TLS' (18)
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Re-binding socket to listen for VNC connections on TCP port 5900 in (a...nterface
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Listening IPv6://[::]:5900
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Listening IPv4://0.0.0.0:5900
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Clearing securityTypes
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Advertising security type: 'TLS' (18)
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Clearing securityTypes
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Advertising security type: 'TLS' (18)
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Advertising authentication type: 'No Authentication' (1)
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Re-binding socket to listen for VNC connections on TCP port 5900 in (a...nterface
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Listening IPv6://[::]:5900
Oct 04 10:02:13 payalG-PC gnome-session[4719]: 04/10/2018 10:02:13 AM Listening IPv4://0.0.0.0:5900
Oct 04 10:02:13 payalG-PC org.gtk.vfs.AfcVolumeMonitor[4580]: Volume monitor alive
Oct 04 10:02:14 payalG-PC fwupd[4989]: (fwupd:4989): Fu-WARNING **: ignoring add-delay as device usb:00:04 already pending
Oct 04 10:02:14 payalG-PC fwupd[4989]: (fwupd:4989): Fu-WARNING **: disabling plugin because: failed to coldplug raspberrypi: Raspberry PI ...start.elf
Oct 04 10:02:14 payalG-PC dbus[1034]: [system] Successfully activated service 'org.freedesktop.fwupd'
Oct 04 10:02:14 payalG-PC systemd[1]: Started Firmware update daemon.
Oct 04 10:02:19 payalG-PC gnome-session[4719]: Nautilus-Share-Message: Called "net usershare info" but it failed: Failed to execute child pr...rectory)
Oct 04 10:02:20 payalG-PC org.gnome.ScreenSaver[4580]: ** Message: Lost the name, shutting down.
Oct 04 10:02:25 payalG-PC systemd-logind[1075]: Removed session c1.
Oct 04 10:02:25 payalG-PC systemd[1]: Stopping User Manager for UID 108...
Oct 04 10:02:25 payalG-PC gnome-session[4719]: (vino-server:4937): GLib-CRITICAL **: the GVariant format string '(u)' has a type of '(u)' bu... of '()'
Oct 04 10:02:25 payalG-PC gnome-session[4719]: (vino-server:4937): GLib-CRITICAL **: g_variant_get: assertion 'valid_format_string (format_s...' failed
Oct 04 10:02:25 payalG-PC gnome-session[4719]: (vino-server:4937): GLib-CRITICAL **: the GVariant format string '(u)' has a type of '(u)' bu... of '()'
Oct 04 10:02:25 payalG-PC gnome-session[4719]: (vino-server:4937): GLib-CRITICAL **: g_variant_get: assertion 'valid_format_string (format_s...' failed
Oct 04 10:02:25 payalG-PC systemd[1715]: Stopped target Default.
Oct 04 10:02:25 payalG-PC systemd[1715]: Stopped target Basic System.
Oct 04 10:02:25 payalG-PC systemd[1715]: Stopped target Paths.
Oct 04 10:02:25 payalG-PC systemd[1715]: Stopped target Timers.
Oct 04 10:02:25 payalG-PC systemd[1715]: Stopped target Sockets.
Oct 04 10:02:25 payalG-PC systemd[1715]: Reached target Shutdown.
Oct 04 10:02:25 payalG-PC systemd[1715]: Starting Exit the Session...
Oct 04 10:02:25 payalG-PC systemd[1715]: Received SIGRTMIN+24 from PID 5212 (kill).
Oct 04 10:02:25 payalG-PC systemd[1724]: pam_unix(systemd-user:session): session closed for user lightdm
Oct 04 10:02:25 payalG-PC systemd[1]: Stopped User Manager for UID 108.
Oct 04 10:02:25 payalG-PC systemd[1]: Removed slice User Slice of lightdm.
Oct 04 10:02:25 payalG-PC gnome-session[4719]: (vino-server:4937): GLib-CRITICAL **: the GVariant format string '(u)' has a type of '(u)' bu... of '()'
Oct 04 10:02:25 payalG-PC gnome-session[4719]: (vino-server:4937): GLib-CRITICAL **: g_variant_get: assertion 'valid_format_string (format_s...' failed
Oct 04 10:02:28 payalG-PC gnome-keyring-daemon[4492]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
Oct 04 10:02:28 payalG-PC gnome-keyring-daemon[4492]: asked to register item /org/freedesktop/secrets/collection/login/144, but it's already registered
Oct 04 10:02:28 payalG-PC gnome-keyring-daemon[4492]: asked to register item /org/freedesktop/secrets/collection/login/143, but it's already registered
Oct 04 10:02:33 payalG-PC org.gnome.zeitgeist.Engine[4580]: ** (zeitgeist-datahub:5268): WARNING **: zeitgeist-datahub.vala:229: Unable to ge...he bus!
Oct 04 10:02:35 payalG-PC dbus[1034]: [system] Failed to activate service 'org.bluez': timed out
Oct 04 10:02:35 payalG-PC pulseaudio[4815]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Fai...imed out
Oct 04 10:03:01 payalG-PC CRON[5305]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:03:01 payalG-PC CRON[5306]: (payal) CMD (./cleanJob.sh)
Oct 04 10:03:01 payalG-PC CRON[5305]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:03:01 payalG-PC CRON[5305]: pam_unix(cron:session): session closed for user payal
Oct 04 10:03:04 payalG-PC dbus[1034]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Oct 04 10:03:08 payalG-PC gnome-keyring-daemon[4492]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
Oct 04 10:03:09 payalG-PC gnome-keyring-daemon[4492]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
Oct 04 10:03:20 payalG-PC dbus[1034]: [system] Activating service name='org.debian.apt' (using servicehelper)
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: Traceback (most recent call last):
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/sbin/aptd", line 37, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: import aptdaemon.core
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/aptdaemon/core.py", line 52, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: from gi.repository import GObject, GLib
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/gi/init.py", line 42, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: from . import _gi
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: ImportError: cannot import name '_gi'
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: Error in sys.excepthook:
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: Traceback (most recent call last):
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: from apport.fileutils import likely_packaged, get_recent_crashes
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/apport/init.py", line 5, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: from apport.report import Report
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: import apport.fileutils
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: from apport.packaging_impl import impl as packaging
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: import apt
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/apt/init.py", line 23, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: import apt_pkg
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: ModuleNotFoundError: No module named 'apt_pkg'
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: Original exception was:
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: Traceback (most recent call last):
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/sbin/aptd", line 37, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: import aptdaemon.core
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/aptdaemon/core.py", line 52, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: from gi.repository import GObject, GLib
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: File "/usr/lib/python3/dist-packages/gi/init.py", line 42, in
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: from . import _gi
Oct 04 10:03:20 payalG-PC org.debian.apt[1034]: ImportError: cannot import name '_gi'
Oct 04 10:03:20 payalG-PC dbus[1034]: [system] Activated service 'org.debian.apt' failed: Launch helper exited with unknown return code 1
Oct 04 10:03:20 payalG-PC gnome-session[4719]: (gnome-software:4915): Gs-WARNING **: failed to call gs_plugin_refresh on apt: GDBus.Error:or...n code 1
Oct 04 10:03:30 payalG-PC dbus[1034]: [system] Failed to activate service 'org.bluez': timed out
Oct 04 10:03:50 payalG-PC snapd[1197]: storehelpers.go:398: cannot refresh: snap has no updates available: "core", "core18", "gimp", "postman"
Oct 04 10:03:50 payalG-PC snapd[1197]: autorefresh.go:387: auto-refresh: all snaps are up-to-date
Oct 04 10:03:54 payalG-PC dbus[1034]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.....service'
Oct 04 10:03:54 payalG-PC systemd[1]: Starting Hostname Service...
Oct 04 10:03:54 payalG-PC dbus[1034]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct 04 10:03:54 payalG-PC systemd[1]: Started Hostname Service.
Oct 04 10:04:01 payalG-PC CRON[5660]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:04:01 payalG-PC CRON[5661]: (payal) CMD (./cleanJob.sh)
Oct 04 10:04:01 payalG-PC CRON[5660]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:04:01 payalG-PC CRON[5660]: pam_unix(cron:session): session closed for user payal
Oct 04 10:04:05 payalG-PC org.gtk.vfs.Daemon[4580]: got no contact to IPC$
Oct 04 10:04:05 payalG-PC org.gtk.vfs.Daemon[4580]: ** (gvfsd:4646): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): ...med out
Oct 04 10:04:05 payalG-PC org.gtk.vfs.Daemon[4580]: ** (process:5610): WARNING **: Couldn't create directory monitor on smb://x-gnome-default...mounted
Oct 04 10:04:05 payalG-PC org.gtk.vfs.Daemon[4580]: ** (process:5610): WARNING **: Couldn't create directory monitor on smb://x-gnome-default...mounted
Oct 04 10:04:05 payalG-PC org.gtk.vfs.Daemon[4580]: ** (process:5610): WARNING **: Couldn't create directory monitor on smb://x-gnome-default...mounted
Oct 04 10:04:05 payalG-PC org.gtk.vfs.Daemon[4580]: ** (process:5616): WARNING **: Couldn't create directory monitor on smb://x-gnome-default...backend
Oct 04 10:05:01 payalG-PC CRON[5714]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:05:01 payalG-PC CRON[5715]: (payal) CMD (./cleanJob.sh)
Oct 04 10:05:01 payalG-PC CRON[5714]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:05:01 payalG-PC CRON[5714]: pam_unix(cron:session): session closed for user payal
Oct 04 10:06:01 payalG-PC CRON[5729]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:06:01 payalG-PC CRON[5730]: (payal) CMD (./cleanJob.sh)
Oct 04 10:06:01 payalG-PC CRON[5729]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:06:01 payalG-PC CRON[5729]: pam_unix(cron:session): session closed for user payal
Oct 04 10:07:01 payalG-PC CRON[5741]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:07:01 payalG-PC CRON[5742]: (payal) CMD (./cleanJob.sh)
Oct 04 10:07:01 payalG-PC CRON[5741]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:07:01 payalG-PC CRON[5741]: pam_unix(cron:session): session closed for user payal
Oct 04 10:08:01 payalG-PC CRON[5752]: pam_unix(cron:session): session opened for user payal by (uid=0)
Oct 04 10:08:01 payalG-PC CRON[5753]: (payal) CMD (./cleanJob.sh)
Oct 04 10:08:01 payalG-PC CRON[5752]: (CRON) info (No MTA installed, discarding output)
Oct 04 10:08:01 payalG-PC CRON[5752]: pam_unix(cron:session): session closed for user payal

i am not able to pin point the actual issue here.

@payalgaikwad42

This comment has been minimized.

payalgaikwad42 commented Oct 4, 2018

when i use following link to update iotedge on my system still i am getting the same issue:
https://azure.microsoft.com/en-us/updates/iot-edge1-0-2/

in meanwhile, can you provide me with the steps to download the previous version of GA?

@neumanndaniel

This comment has been minimized.

Member

neumanndaniel commented Oct 8, 2018

Had the same issue and identified it with journalctl --no-pager

Issue:

Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [INFO] - Initializing hsm...
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] - An hsm error occurred.
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] - caused by: HSM failure
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] - caused by: HSM Init failure: 44
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_pki_openssl.c:validate_certificate_expiration:655) Certificate has expired
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_pki_openssl.c:check_certificates:1366) Certificate file has expired /var/lib/iotedge/hsm/certs/edge_owner_cav0cQJsrFHjxosiOJDer2oKf-O45ZXKVJrO5WFWtFKe0_.cert.pem
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:load_if_cert_and_key_exist_by_alias:1531) Failure when verifying certificate for alias edge_owner_ca
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:generate_edge_hsm_certificates_if_needed:1638) Could not check and load owner CA certificate and key
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_store.c:hsm_provision_edge_certificates:1804) Failure generating required HSM certificates
Oct 08 16:54:49 rp3-01 iotedged[748]: 2018-10-08T14:54:49Z [ERR!] (/project/hsm-sys/azure-iot-hsm-c/src/edge_hsm_client_crypto.c:hsm_client_crypto_init:43) Could not create store. Error code 1915

It was the expired edge_owner certificate under /var/lib/iotedge/hsm/certs/.

Solution:

I deleted the edge_owner certificate and rebooted the iotedge daemon to generate a new one.

sudo systemctl restart iotedge

@myagley

This comment has been minimized.

Contributor

myagley commented Oct 8, 2018

@neumanndaniel thanks for the heads up. we have a fix for this in the upcoming release.

@payalgaikwad42 is this a new setup or has IoT Edge been running before? You can try apt-get purge libiothsm iotedge and then try running through the installation steps again.

@payalgaikwad42

This comment has been minimized.

payalgaikwad42 commented Oct 9, 2018

@neumanndaniel Thank you very much.
This solved my problem it was the expired edge_owner certificate in my case as well.
@myagley IoT Edge was running before the new update. Now its running again by following the steps provided by @neumanndaniel.
Thank you for the help.
Closing this issue.

@ralarcon

This comment has been minimized.

ralarcon commented Oct 23, 2018

@myagley would this issue affect to v1.0.1 too? We are having the same effect on IoT Edge Devices deployed with 1.0.1 runtime & edgeAgent version....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment