[BlueOnyx:25425] Re: web problems on new 5210R load

[Larry Smith]

Michael,

  Thanks for the input.  Double checked the switch
and router and even changed the new (copied) site
to another IP and still no luck.  And that would not
account for the first site (coming-soon page) not
responding after the migrate, completely different
IP and name.

 In looking I did see that httpd is apparently restarting
itself (or something is) every 15 minutes.

<quote>
[Tue May 17 12:30:05.931176 2022] [core:notice] [pid 1781999] AH00094: Command
 line: '/usr/sbin/httpd -D FOREGROUND'
...
[Tue May 17 12:45:05.464207 2022] [core:notice] [pid 1782851] AH00094: Command 
line: '/usr/sbin/httpd -D FOREGROUND'
...
[Tue May 17 13:00:06.127938 2022] [core:notice] [pid 1783862] AH00094: Command 
line: '/usr/sbin/httpd -D FOREGROUND'
</quote>

and appears to coincide with the reported certificate errors.

Tried an SSH to the migrated site's new IP and it worked
so the box recognizes the IP and site, but httpd apparently
does not.

Still looking.

-- 
Larry Smith
lesmith at ecsis.net

On Tue May 17 2022 12:20, Michael Stauber wrote:
> Hi Larry,
>
> > Just loaded a new(ish) 5210R server and ran the
> > basic box a few days to make sure everything was
> > working.  Purchased and loaded AV-SPAM, PHP, and
> > Roundcube.  Loaded two sites on last week, one brand-new,
> > coming-soon page, the other migrated from a 5209R
> > server.  When I first did the completely new site
> > it was working fine (coming soon page displayed
> > on call and roundcube was working for mail)
> >
> > Once I did the easy-migrate the individual sites
> > no longer work (just timeout) and httpd does not
> > seem to be answering for their IP, only the box
> > IP.
>
> This could be related to a couple of things:
>
> The switch still has the MAC addresses for the IPs from when they were
> used on the old server. So traffic to the Vsite IPs might not yet go to
> the new server until the switch clears its ARP table.
>
> If the traffic actually makes it to the new server? You should be able
> to see that in the Apache logfiles.
>
> If the traffic comes in, but the pages don't load? This could be due to
> .htaccess files in /web, but the server not being configured to allow
> .htaccess.
>
> Or it could be related to the PHP method or version.
>
> Or maybe Apache just needs another restart (yeah, that happens).
>
> If you can't shake it loose, then please file a support ticket via the
> GUI of the new server and make sure to tick the checkbox "Allow Access"
> and I'll take a look.
>
> > Also getting the following in the httpd error_log:
> >
> > <quote>
> > [Tue May 17 11:45:05.729533 2022] [ssl:error] [pid 1778674] AH02604:
> > Unable to configure certificate server.domain.net:443:0 for stapling
> > [Tue May 17 11:45:05.729995 2022] [ssl:error] [pid 1778674] AH02217:
> > ssl_stapling_init_cert: can't retrieve issuer certificate! [subject:
> > CN=server.domain.net / issuer: CN=R3,O=Let's Encrypt,C=US / serial:
> > 037322C7D1A740B6608CD833D5BEE0B1AA74 / notbefore: Apr 25 11:22:11 2022
> > GMT / notafter: Jul 24 11:22:10 2022 GMT]
> > </quote>
>
> That can be ignored and isn't related.