RL 10.1 (minor) odd issue (and resolution)

hi all -

interesting (minor) issue on RL 10.1

systemctl status httpd.service; gave me the following message:

httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS

this appears to fix it as per this link:

cat  /etc/systemd/system/httpd.service.d/override.conf   ;
[Service]
ExecStart=
ExecStart=/usr/sbin/httpd -DFOREGROUND
END

systemctl daemon-reload              ;
systemctl  restart  httpd.service    ;

thoughts or suggestions?

i realize that rocky-linux 10 is still a bit experimental. notice that even Mariadb 11.4 does not support it (yet)

SYSTEM INFORMATION
OS type and version RL 10.1
Webmin version 2.621
Virtualmin version 8.1
Webserver version REQUIRED
Related packages SUGGESTED

Rocky 10 support is not experimental. And, we don’t use Mariadb from upstream, we use the one that ships from the Rocky (or RHEL or Alma repos).

It’s not clear to me what the source of the problem is. The thread you linked indicates maybe a restore of Apache config/files from an older system? I haven’t seen this error, but I don’t have a lot of Rocky 10 boxes running Apache.

We don’t provide the Apache package, so if it’s a package bug, it’s a Rocky problem, but that thread indicates a fresh install doesn’t have the problem. So, it’s either something on your system or something the Virtualmin installer did (but I didn’t see it in my testing). We’d need to know specifically what causes the problem, rather than just the workaround.

Rocky 10 support is not experimental.

sorry, i meant MariaDB, not webmin. Mariadb has yet to support RL-10. this is cetainly NOT a webmin issue, more of a personal rant. (but the RHEL package appears to work just fine)

httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS

i just now went to google-VM and created a RL-10.1 instance. then i did my favorite command:

 sh -c "$(curl -fsSL https://software.virtualmin.dev/virtualmin-install.sh)"  \
                                             --                               \
                                             --bundle LAMP                    \
                                             --branch   stable                \
                                             --hostname host.DOMAIN.COM       \
                                             --yes                            ;

the message seems like its more of a status notice, not necessarily an error. i just thought it would be worth mentioning.

EDIT: i call it my fav command because i remember what it was like trying to “rush” a RL installation when RL first came out, and what problems that caused me. i am beyond thrilled that such a simple yet elegant command can do so much in such a short amount of time. this is personally very exciting for me.

That’s a development version of the install script. If you’re doing anything other than testing development features, you probably want the stable version linked on our download page: Downloading and Installing | Virtualmin — Open Source Web Hosting Control Panel

I don’t know that Ilia currently has experimental stuff in the installer on the dev repo, but I don’t know that he doesn’t.

thank you - i am trying the “correct” link now. not sure how i missed that…?

EDIT: i had the same results with
https://software.virtualmin.dev/virtualmin-install.sh
as i did with
https://download.virtualmin.com/virtualmin-install

i downloaded both and ran a diff, they are identical.

They are identical only because no work is currently being done on the Virtualmin install script.

To be clear, Virtualmin doesn’t create this file, and it shouldn’t exist on a clean Rocky 10 installation. Neither of my systems has this file.

i was following Joes suggestion.

i understand this, however this was only suggested as a workaround on the RL forum.

interesting development: for fun, i created BOTH a google-VM and a virtualbox RL-10.1, then:
systemctl start httpd; systemctl status httpd;
and the issue persists. so this is probably not a webmin issue. sorry, I probably should have tried this first.

i will mention this on the RL forum.

EDIT: this appears to be a situation in Fedora as well and the message can be safely ignored as i originally suspected.

1 Like

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.