Undefined subroutine &main::get_jabber_status called at ./status-lib.pl line 201.
ejabberd wasn’t supposed to be running anymore so I stopped it. I’ll probably remove the package. In the meantime I get an email every five minutes about this.
I just used the interface to stop it from coming up at boot. I thought I’d done this before, so, let’s just call this a note to myself that I did it.
So, it’s a bug that we’d be calling a nonexistent function.
But, you can just remove that status monitor in System and Server Status to make the error go away. It’s something you would have added, as ejabberd is definitely not a default monitor.
Er, but also, I can’t even find such a function in our repo. I don’t know where it came from, as I don’t think it was ever in Webmin. Did you install a Webmin module for ejabberd, maybe? Maybe it came with such a status monitor?
The 173… was the one grep said to look at. Removed and restarted webmin. Emails stopped.
To recap though, before the upgrade, the service was running and there had been no problems. After upgrade, the service was still running but the error emails started.
I thought it was disable but it was running. Not sure why but that is a red herring here. Personally I wouldn’t spend too many cycles on it.
Oh, I’m not spending any cycles on it. It wasn’t our code that broke. I’m assuming there was an ejabberd module installed on whatever system you restored a backup from, and that it included a status check function…not having that module any more obviously means that code is gone, so Webmin can’t call it.
Oh, apparently it was included in Webmin until recently. Weird. I didn’t even know that. So, it’s bug-like that a missing status function from a removed module results in a Perl error…users should never see Perl errors unless something terrible and unpredictable has happened. Removing modules is predictable, so it should probably be a comprehensible error.
@Jamie if you have free time, maybe a missing status function shouldn’t result in a confusing Perl error.
