On 16/6/20 5:34 pm, Anthony K wrote:
The new way to do this is exactly what Gordon suggested - using
`systemctl edit ` creates an override in
`/etc/systemd/system/httpd.service.d/override.conf`.
The only issue is that there is no `systemctl` related command to
remove this override - you will
Thank you Gordon. That works for me. 8.2 needs the same fix.
Alan
On 16/06/2020 16:21, Gordon Messmer wrote:
On 6/15/20 7:06 PM, Jay Hart wrote:
If I do 'systemctl start httpd', apache will start right up. But
during boot, it doesn't and I
get the resulting errors below.
Jun 15 21:17:28 dre
Thanks to all that responded. Gordon's suggestion worked brilliantly. I ran
the suggested
command, saved the file, rebooted, apache came right up.
Can't thank you guys enough.
Now, lets try to solve my intermittent connectivity issue, more on that later...
Jay
> On 16/6/20 4:15 pm, Alessandro
On 16/6/20 4:15 pm, Alessandro Baggi wrote:
Note: when you will get update for httpd package all could be reverted
to the original status, so to avoid that your modified httpd.service
will get an overwrite, create an alternative httpd.service in
/etc/systemd/system (if I'm not wrong).
Proba
Just a wild guess, but it sounds like Apache is being started before the
network is online.Is this host simple static Ethernet or DHCP, or is it
something more complicated like WiFi?
I believe you can set service dependencies with systemd, ideally your
apache service isn't started before the n
>
>
> Il 16/06/20 08:11, Alessandro Baggi ha scritto:
>>
>>
>> Il 16/06/20 06:21, Gordon Messmer ha scritto:
>>> On 6/15/20 7:06 PM, Jay Hart wrote:
If I do 'systemctl start httpd', apache will start right up. But
during boot, it doesn't and I
get the resulting errors below.
>>
Il 16/06/20 08:11, Alessandro Baggi ha scritto:
Il 16/06/20 06:21, Gordon Messmer ha scritto:
On 6/15/20 7:06 PM, Jay Hart wrote:
If I do 'systemctl start httpd', apache will start right up. But
during boot, it doesn't and I
get the resulting errors below.
Jun 15 21:17:28 dream httpd[15
Il 16/06/20 06:21, Gordon Messmer ha scritto:
On 6/15/20 7:06 PM, Jay Hart wrote:
If I do 'systemctl start httpd', apache will start right up. But
during boot, it doesn't and I
get the resulting errors below.
Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested
address: AH00072:
On 6/15/20 7:06 PM, Jay Hart wrote:
If I do 'systemctl start httpd', apache will start right up. But during boot,
it doesn't and I
get the resulting errors below.
Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address:
AH00072: make_sock: could
not bind to address 10.20.30.11:
On 6/15/2020 7:06 PM, Jay Hart wrote:
Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address:
AH00072: make_sock: could
not bind to address 10.20.30.11:80
Could some transient service be holding port 80 at that time?
You could probably arrange to run a script that runs "lsof -
I have always had exactly the same problem. I had to write a script and
run it at boot time:
sleep 10
/usr/bin/systemctl start httpd
Must be some timing problem with the interface addresses not being set
up in time.
Alan
On 16/06/2020 14:06, Jay Hart wrote:
If I do 'systemctl start httpd',
If I do 'systemctl start httpd', apache will start right up. But during boot,
it doesn't and I
get the resulting errors below.
Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address:
AH00072: make_sock: could
not bind to address 10.20.30.11:80
Jun 15 21:17:28 dream httpd[1534]:
12 matches
Mail list logo
