Project

General

Profile

Bug #67915

Service stopped in web UI but actually it's running

Added by Stilez y 10 months ago. Updated 9 months ago.

Status:
Closed
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Need additional information from Author
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

See attached screenshot (combines 3 items: webUI, ps output, and messages log)

I'm having issues configuring upsmon service, but that's not so relevant. The interesting thing is that it keeps trying to start the service, and does in fact start it, after repeated reboots, even though it's configured not to start when I check in the web UI. When I look at the web UI, it states incorrewctly that the service isn't running when in fact it is running, as can be seen in the other output.

Surely something wrong with that? :)

ups.png (56.7 KB) ups.png Stilez y, 01/06/2019 03:50 AM
47712

Related issues

Related to FreeNAS - Bug #65544: Do not start S3 service at boot if 'Start Automatically' is not checkedDone

History

#1 Updated by Dru Lavigne 10 months ago

  • Related to Bug #65544: Do not start S3 service at boot if 'Start Automatically' is not checked added

#2 Updated by Dru Lavigne 10 months ago

  • Category changed from GUI (new) to Middleware
  • Assignee changed from Release Council to William Grzybowski

#3 Updated by William Grzybowski 10 months ago

  • Assignee changed from William Grzybowski to Vladimir Vinogradenko
  • Target version changed from Backlog to 11.2-U2

#4 Updated by Vladimir Vinogradenko 10 months ago

  • Status changed from Unscreened to Blocked
  • Reason for Blocked set to Waiting for feedback

Stilez, can you please post output of

echo "select * from services_services" | sqlite3 /data/freenas-v1.db

#5 Updated by Stilez y 10 months ago

I should say, I did eventually kill this by ps -awx| grep ups and then a combination of killall ups... and kill PID. It was resistant to being killed, but eventually died, apparently I managed to kill the controlling ups process of something. It had survived many reboots, but hasn't come back since. I don't know why, as I wouldn't expect that to affect what happened on the next reboot. But apparently it got stuck somehow, and it did stop it restarting.

Here's the config database at present. I could go back to recent config backups from a week or so ago, and probe them the same way, to confirm what they would have said. Would that help?

  # echo "select * from services_services" | sqlite3 /data/freenas-v1.db
2|afp|0
4|cifs|1
5|dynamicdns|0
6|ftp|0
7|iscsitarget|0
9|nfs|0
10|snmp|0
11|ssh|1
12|tftp|0
14|ups|0
16|rsync|0
18|smartd|1
20|domaincontroller|0
21|lldp|0
22|webdav|0
23|s3|0
24|netdata|0

#6 Updated by Vladimir Vinogradenko 10 months ago

Stilez, can you also post output of

cat /var/tmp/rc.conf.freenas

please?

I struggle to understand why upsmon is being started on boot, it's clearly disabled

#7 Updated by Dru Lavigne 10 months ago

  • Target version changed from 11.2-U2 to 11.2-U3

#8 Updated by Dru Lavigne 9 months ago

  • Status changed from Blocked to Closed
  • Target version changed from 11.2-U3 to N/A
  • Reason for Blocked changed from Waiting for feedback to Need additional information from Author

Also available in: Atom PDF