[users@httpd] Issues with files accessed over NFS
Although I realize that this question is more about NFS than Apache it still concerns my web server so here goes. This is at work so a bit of history first, sorry for the novel length email in advance. The set up I have was already in existence when I started my current position. The web server, running Apache on top of Debian 8, was directly connected to a storage server, also on Debian 8, via a dedicated 10Gbps network link. The storage was accessed via NFS mounts, different mounts for different areas in order to section them off within the website with aliases. Not all of the website was stored on the server, just the ones that used the most disk space. Of course this was three years ago and Debian 8 went EOL. Before that occurred it was my job to upgrade the servers to a later version of Debian. In order to keep the distribution upgrades as far apart as possible I went with Debian 11, upgrading on a path from 9 to 10 to 11. During the upgrade all services were checked out for basic functionality and no problems were seen. Not long after the upgrade an interesting problem was apparent. Files accessed over NFS were not downloading properly. The download would start but then stop anywhere from 30% to 60%. These files were not large with the smallest ones being just over 1MB. Any file stored on the web server itself downloaded just fine, no matter the size. I checked just about everything on that connection from the cable, which was only 1 foot in length so I got a longer one, to the NFS mount options. Changes were made but they did not seem to make a difference and all file transfer tests done within the OS itself worked fine with files up to 100MB tested. The only thing I did not check until recently was the NFS version. The mounts were automatically using NFSv4 which I considered, at this point in its development, to be stable. However when I switched to NFSv3 the problem went away. So after all that I seemed to have "solved" it by dropping back to an older version of NFS. So the questions I have for the community are: Has anyone seen a similar issue and solved it? If so did you find another solution other than reverting to NFSv3? Thanks, Chris Woelkers
Re: [users@httpd] Issues with files accessed over NFS
check the mount options for the NFS mount on apache server as well as the underlying file system on the NFS server. unless needed, set to noatime and nodiratime From: Chris Woelkers - NOAA Federal Sent: Thursday, June 30, 2022 3:07:01 PM To: users@httpd.apache.org Subject: [users@httpd] Issues with files accessed over NFS Although I realize that this question is more about NFS than Apache it still concerns my web server so here goes. This is at work so a bit of history first, sorry for the novel length email in advance. The set up I have was already in existence when I started my current position. The web server, running Apache on top of Debian 8, was directly connected to a storage server, also on Debian 8, via a dedicated 10Gbps network link. The storage was accessed via NFS mounts, different mounts for different areas in order to section them off within the website with aliases. Not all of the website was stored on the server, just the ones that used the most disk space. Of course this was three years ago and Debian 8 went EOL. Before that occurred it was my job to upgrade the servers to a later version of Debian. In order to keep the distribution upgrades as far apart as possible I went with Debian 11, upgrading on a path from 9 to 10 to 11. During the upgrade all services were checked out for basic functionality and no problems were seen. Not long after the upgrade an interesting problem was apparent. Files accessed over NFS were not downloading properly. The download would start but then stop anywhere from 30% to 60%. These files were not large with the smallest ones being just over 1MB. Any file stored on the web server itself downloaded just fine, no matter the size. I checked just about everything on that connection from the cable, which was only 1 foot in length so I got a longer one, to the NFS mount options. Changes were made but they did not seem to make a difference and all file transfer tests done within the OS itself worked fine with files up to 100MB tested. The only thing I did not check until recently was the NFS version. The mounts were automatically using NFSv4 which I considered, at this point in its development, to be stable. However when I switched to NFSv3 the problem went away. So after all that I seemed to have "solved" it by dropping back to an older version of NFS. So the questions I have for the community are: Has anyone seen a similar issue and solved it? If so did you find another solution other than reverting to NFSv3? Thanks, Chris Woelkers
Re: [users@httpd] Issues with files accessed over NFS
The underlying filesystem is ZFS and the drives, all 28 of them, are in good health. I'll check those options out. Thanks, Chris Woelkers IT Specialist National Oceanic and Atmospheric Administration Great Lakes Environmental Research Laboratory 4840 S State Rd | Ann Arbor, MI 48108 Office: 734-741-2446 Cell: 734-604-0059 Voice: 734-219-3815 On Thu, Jun 30, 2022 at 3:22 PM Bender, Charles wrote: > check the mount options for the NFS mount on apache server as well as the > underlying file system on the NFS server. unless needed, set to noatime and > nodiratime > -- > *From:* Chris Woelkers - NOAA Federal > *Sent:* Thursday, June 30, 2022 3:07:01 PM > *To:* users@httpd.apache.org > *Subject:* [users@httpd] Issues with files accessed over NFS > > Although I realize that this question is more about NFS than Apache it > still concerns my web server so here goes. This is at work so a bit of > history first, sorry for the novel length email in advance. > > The set up I have was already in existence when I started my current > position. The web server, running Apache on top of Debian 8, was directly > connected to a storage server, also on Debian 8, via a dedicated 10Gbps > network link. The storage was accessed via NFS mounts, different mounts for > different areas in order to section them off within the website with > aliases. Not all of the website was stored on the server, just the ones > that used the most disk space. > Of course this was three years ago and Debian 8 went EOL. Before that > occurred it was my job to upgrade the servers to a later version of Debian. > In order to keep the distribution upgrades as far apart as possible I went > with Debian 11, upgrading on a path from 9 to 10 to 11. During the upgrade > all services were checked out for basic functionality and no problems were > seen. > Not long after the upgrade an interesting problem was apparent. Files > accessed over NFS were not downloading properly. The download would start > but then stop anywhere from 30% to 60%. These files were not large with the > smallest ones being just over 1MB. Any file stored on the web server itself > downloaded just fine, no matter the size. I checked just about everything > on that connection from the cable, which was only 1 foot in length so I got > a longer one, to the NFS mount options. Changes were made but they did not > seem to make a difference and all file transfer tests done within the OS > itself worked fine with files up to 100MB tested. > The only thing I did not check until recently was the NFS version. The > mounts were automatically using NFSv4 which I considered, at this point in > its development, to be stable. However when I switched to NFSv3 the problem > went away. So after all that I seemed to have "solved" it by dropping back > to an older version of NFS. > > So the questions I have for the community are: Has anyone seen a similar > issue and solved it? If so did you find another solution other than > reverting to NFSv3? > > Thanks, > > Chris Woelkers >
[users@httpd] NameVirtualHost fails
I'm using SUSE Leap 15.3 and apache2. I'm trying to get SSL to work on two hosts with the same IP address. My vhosts.config is set for the two hosts but only one actually runs. When I run systemctl status apache2.service I get a message that NameVirtualHost has no effect and will be removed. So the configuration only works if I have just one host. What key detail am I missing in the network configuration? Thanks, Jack Nilles
Re: [users@httpd] NameVirtualHost fails
On Thu, Jun 30, 2022 at 4:28 PM jnil...@jala.com wrote: > > I'm using SUSE Leap 15.3 and apache2. I'm trying to get SSL to work on two > hosts with the same IP address. My vhosts.config is set for the two hosts but > only one actually runs. When I run systemctl status apache2.service I get a > message that NameVirtualHost has no effect and will be removed. So the > configuration only works if I have just one host. That directive has no effect, it's not the cause of any issue. > What key detail am I missing in the network configuration? What are your Listen directives? What do your virtualHosts look like? What test requests do you send and how do they fail? - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
RE: [users@httpd] NameVirtualHost fails
You are missing something called virtual hosts. You are allowed one host but you can have many virtual hosts. Secondly, you should be using Leap 15.4, it sounds like you are out of date, sorry to say. If you go to your httpd.conf file then you will notice that there is a enable virtual hosts #include virtual hosts.conf httpd-vhosts.conf so uncomment it remove the # De : jnil...@jala.com Envoyé : jeudi 30 juin 2022 16:28 À : users@httpd.apache.org Objet : [users@httpd] NameVirtualHost fails I'm using SUSE Leap 15.3 and apache2. I'm trying to get SSL to work on two hosts with the same IP address. My vhosts.config is set for the two hosts but only one actually runs. When I run systemctl status apache2.service I get a message that NameVirtualHost has no effect and will be removed. So the configuration only works if I have just one host. What key detail am I missing in the network configuration? Thanks, Jack Nilles
Re: [users@httpd] Issues with files accessed over NFS
Am 30.06.2022 um 21:07 schrieb Chris Woelkers - NOAA Federal: Although I realize that this question is more about NFS than Apache it still concerns my web server so here goes. This is at work so a bit of history first, sorry for the novel length email in advance. The set up I have was already in existence when I started my current position. The web server, running Apache on top of Debian 8, was directly connected to a storage server, also on Debian 8, via a dedicated 10Gbps network link. The storage was accessed via NFS mounts, different mounts for different areas in order to section them off within the website with aliases. Not all of the website was stored on the server, just the ones that used the most disk space. Of course this was three years ago and Debian 8 went EOL. Before that occurred it was my job to upgrade the servers to a later version of Debian. In order to keep the distribution upgrades as far apart as possible I went with Debian 11, upgrading on a path from 9 to 10 to 11. During the upgrade all services were checked out for basic functionality and no problems were seen. Not long after the upgrade an interesting problem was apparent. Files accessed over NFS were not downloading properly. The download would start but then stop anywhere from 30% to 60%. These files were not large with the smallest ones being just over 1MB. Any file stored on the web server itself downloaded just fine, no matter the size. I checked just about everything on that connection from the cable, which was only 1 foot in length so I got a longer one, to the NFS mount options. Changes were made but they did not seem to make a difference and all file transfer tests done within the OS itself worked fine with files up to 100MB tested. The only thing I did not check until recently was the NFS version. The mounts were automatically using NFSv4 which I considered, at this point in its development, to be stable. However when I switched to NFSv3 the problem went away. So after all that I seemed to have "solved" it by dropping back to an older version of NFS. So the questions I have for the community are: Has anyone seen a similar issue and solved it? If so did you find another solution other than reverting to NFSv3? Try disabling sendfile and mmap: https://httpd.apache.org/docs/2.4/en/mod/core.html#enablesendfile https://httpd.apache.org/docs/2.4/en/mod/core.html#enablemmap If that helps, check out, which of the two is the culprit. Best regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] NameVirtualHost fails
That is one assumption, sure. Best to have the user run apachectl -S to confirm. For all we know, they could have defined invalid vhosts. On Thu, 30 Jun 2022 at 16:54, wrote: > You are missing something called virtual hosts. You are allowed one host > but you can have many virtual hosts. Secondly, you should be using Leap > 15.4, it sounds like you are out of date, sorry to say. > > > > If you go to your httpd.conf file then you will notice that there is a > enable virtual hosts #include virtual hosts.conf httpd-vhosts.conf so > uncomment it remove the # > > > > *De :* jnil...@jala.com > *Envoyé :* jeudi 30 juin 2022 16:28 > *À :* users@httpd.apache.org > *Objet :* [users@httpd] NameVirtualHost fails > > > > I'm using SUSE Leap 15.3 and apache2. I'm trying to get SSL to work on > two hosts with the same IP address. My vhosts.config is set for the two > hosts but only one actually runs. When I run systemctl status > apache2.service I get a message that NameVirtualHost has no effect and > will be removed. So the configuration only works if I have just one host. > > > > What key detail am I missing in the network configuration? > > > > Thanks, > > > > Jack Nilles > > >
