update-engine.service.d # systemctl status update-engine
● update-engine.service - Update Engine
Loaded: loaded (/usr/lib64/systemd/system/update-engine.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/update-engine.service.d
└─http-proxy.conf
Active: active (running) since Fri 2018-03-30 01:01:00 UTC; 48s ago
Main PID: 1326 (update_engine)
Memory: 2.2M
CPU: 409ms
CGroup: /system.slice/update-engine.service
└─1326 /usr/sbin/update_engine -foreground -logtostderr
Mar 30 01:01:45
lusytp1026.usytp.basf.net update_engine[1326]: [0330/010145:INFO:action_processor.cc(82)] ActionProcessor::ActionComplete: finished Omah...rAction
Mar 30 01:01:45
lusytp1026.usytp.basf.net update_engine[1326]: [0330/010145:INFO:omaha_response_handler_action.cc(36)] There are no updates. Aborting.
Mar 30 01:01:45
lusytp1026.usytp.basf.net update_engine[1326]: [0330/010145:INFO:action_processor.cc(68)] ActionProcessor::ActionComplete: OmahaResponse...essing.
Mar 30 01:01:45
lusytp1026.usytp.basf.net update_engine[1326]: [0330/010145:INFO:action_processor.cc(73)] ActionProcessor::ActionComplete: finished last...rAction
Hint: Some lines were ellipsized, use -l to show in full.
Is there a way to diagnose the problem? Where is the service checking the update? I believe my proxy settings correct (because other nodes updated fine), but still would like to confirm if this node have access.
Any help appreciated.