Re: Problems with apache SSI
Lolke Bijlsma wrote: Hi, I'm running unstable and I'm trying to get server side includes to work with apache. I remove apache and apache-common and then installed it again. So I have the latest httpd.conf. I see it has all the right stuff for server side includes in there as long as mod_include is loaded. So I ran: /usr/sbin/modules-config apache enable mod_include and now mod_include is installed. I checked modules.conf and restarted apache. I've never used that method, I check my Apache config file manually, to enable the line for includes. Have you checked to be sure includes are specifically enabled? I only ask because you don't mention checking /etc/Apache/httpd.conf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with apache SSI
At 10:26 AM 2/18/2004, Stephen wrote: Lolke Bijlsma wrote: I'm running unstable and I'm trying to get server side includes to work with apache. I remove apache and apache-common and then installed it again. So I have the latest httpd.conf. SSI isn't on by default Lolke. I see it has all the right stuff for server side includes in there as long as mod_include is loaded. So I ran: /usr/sbin/modules-config apache enable mod_include and now mod_include is installed. I checked modules.conf and restarted apache. I've never used that method, I check my Apache config file manually, to enable the line for includes. Same here. Does anything show up on the httpd error_log when you try to include? Are you trying to include text, or the output of a script? What do you see on the browser? Marty Landman Face 2 Interface Inc 845-679-9387 This Month's New Quiz --- Past Superbowl Winners Make a Website: http://face2interface.com/Home/Demo.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems with apache SSI
Hi, I'm running unstable and I'm trying to get server side includes to work with apache. I remove apache and apache-common and then installed it again. So I have the latest httpd.conf. I see it has all the right stuff for server side includes in there as long as mod_include is loaded. So I ran: /usr/sbin/modules-config apache enable mod_include and now mod_include is installed. I checked modules.conf and restarted apache. To test SSI I created a very small html page that includes another page: html head titleSome title/title /head body h2Some html code/h2 !--#include file=page.shtml-- /body /html Unfortunately I don't see page.shtml being included. page.shtml exists in the same directory as this test.html file. I tried it both my public_html directory as wel as the document root (/var/www). What am I doing wrong? Like I said before I'm running unstable. apache is: ii apache 1.3.29.0.1-5 Versatile, high-performance HTTP server Thanks, Lolke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PRoblems with apache and VirtualHosts
Hello list ! i have a problem with virtualhosts and the apache server. my debian is: 2.2r0 the problem is: i can only put 2 virtualhost in the configuration file (httpd.conf) because with more virtualhosts the apacheserver did not start ! thanks for all your help and please forgive my bad english !
Re: PRoblems with apache and VirtualHosts
Jan Gehring [EMAIL PROTECTED] writes: i have a problem with virtualhosts and the apache server. my debian is: 2.2r0 the problem is: i can only put 2 virtualhost in the configuration file (httpd.conf) because with more virtualhosts the apacheserver did not start ! It does work - I have 7 virtual hosts running on stable. Did you check the configfile with `apachectl configtest` before starting the server? Most likely, there's an error in the conf-file. -- Tschoe,http://gecius.de/gpg-key.txt - Fingerprint: Jens 1AAB 67A2 1068 77CA 6B0A 41A4 18D4 A89B 28D0 F097 pgp1qJGtprQNR.pgp Description: PGP signature
Problems with apache.
I looked at the bugs on www.debian.org and didn't see mine described, so I thought I bounce it off of this group. I installed potato. That was my first mistake. I haven't been able to get samba working nor will apache work. Nothing seems wrong with the install, but I can't get pages to display right. There is an index.html file in the /var/www directory but apache isn't looking for it there. It seems to be looking in /usr/htdocs. However I get the message, The requested URL / was not found on this server. When I look at the error log I see: [Tue Dec 5 16:17:27 2000] [error] [client 169.238.221.206] File does not exist : /usr/htdocs/ [Tue Dec 5 16:17:49 2000] [error] [client 169.238.221.206] File does not exist : /usr/htdocs/ There is an index.html file in /usr/htdocs, see: It does display it as if it were a text file if I specifically address it (http://chinaberry.peachtree.sgi.com/index.html).
Re: Problems with apache.
If order to get the apache to find your index.html file in /var/www, you have to set DocumentRoot to /var/www Go to /etc/apache and edit httpd.conf file. You need to set DocumentRoot to directory where you want to serve hte default pages from. Andrei -- First there was Explorer... Then came Expedition. This summer Coming to a street near you.. Ford Exterminator. -- Andrei Ivanov http://arshes.dyndns.org [EMAIL PROTECTED] 12402354 --
library problems running Apache
I'm running Debian 2.1 and am trying to install the latest secure version of Apache 1.3.9. It actually installed fine, it's just not starting. When I attempt to start the server, it says it can't open libm.so.5. I'm pretty new to Linux and had no idea how or where to find the library package that contained that library. When I get that kind of error where it's looking for a certain library, how do I go about finding out what .deb package will instgall it? I searched Debian's site for a description of what packages provided, but had no luck. I finally found a .deb file called libc5_5.46-3.deb that actually installed this file on my system. However, when I tried to run Apache, it gave me another error: line 171: 1215 Segmentation fault$HTTD I then chucked the idea of installing the secure version of Apache and installed the latest version, Apache 1.3.12. It installed fine, but once again, when I tried to start the Apache server and it generated a different error: error in loading shared libraries libdb.so.3. Cannot open shared object file: No such file or directory. Where do I find the .deb package that will install libdb.so.3? I seem to be having a major problem with libraries and have no idea what package provides the libraries I need. I can't find a document that lists all the libraries that a certain package provides. Any help would be greatly appreciated. Thanks, John [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com
problems with apache-ssl
I have successfully setup apache, but even though apache-ssl has been configure very similar I still can't get to it from a browser (on port 443). After looking at errors.log, it seems that it is seeing the request but denying access. Here is an excerpt from the log file: date [error] SSL_accept failed date [error] error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request Grief, I hate being ignorant...What could be the problem? === Charles Lewis, Director of Administrative Computing Southwestern Adventist University, Keene, TX (817)556-4720 [EMAIL PROTECTED] FAX (360)397-7952 ===
DHCP and problems with apache, samba etc
When using dhcp, since the hostname doesn't resolve to an IP address right away, there are a few packages that barf, like apache and samba. These appear to attempt to find the IP address from the system name. In the case of dhcp, this may not be known. You can't hardcode an address in the /etc/hosts file, since dhcp may change it. You can't put it in the DNS, same reason. For samba with Micro$oft, it's a catch-22. You can set the MS dns to use WINS for a last-ditch name resolution, which would work if samba had registered with WINS as configured in the smb.conf. But if won't config until it knows its own IP addr. Deadlock. So, I have an extremely small script in /usr/local/bin/dhcp-update-hosts if [ -f /etc/dhcpc/config ] ; then source /etc/dhcpc/config fi if [ -f /etc/dhcpc/hostinfo-$IFACE ] ; then source /etc/dhcpc/hostinfo-$IFACE fi /bin/cp /etc/hosts.src /etc/hosts echo $IPADDR `cat /etc/hostname` /etc/hosts This is kicked of by /etc/cron.d/dhcp-update-hosts every 10 minutes. */10 * * * * root /usr/local/bin/dhcp-update-hosts Very simple, it just checks the /etc/dhcpcd/config file for the interface being used, then uses that to pull the IP address from the /etc/dhcpc/host-info file. This is then added to a pristine copy of the /etc/hosts file. I've also modified the /etc/init.d/dhcpc startup file to include the -c option pointing to the /usr/local/bin/dhcp-update-hosts file, so it gets run as soon as an address is obtained. The end result is that as soon as an address is had, it's in the /etc/hosts file, available for name resolution. Whenever the lease expires and is *not* renewed (replaced with another) there's a maximum window of 10 minutes where /etc/hosts is wrong. That can be easily shortened by modifying the /etc/cron.d/dhcp-update-hosts file. Has anyone else had similar problems ? How did you solve them ? -- Dean Carpenter [EMAIL PROTECTED] 94TT :) Areyes, Inc.[EMAIL PROTECTED] No matter where you go, there you are sayeth Buckaroo across the Eighth Dimension
Problems with apache-ssl
I've installed the package apache-ssl from hamm/non-US distribution. The installation didn't cause any problems, but when I tried to connect to my server: lynx localhost:443 I received the error: Alert!: Unexpected network read error; connection aborted. And then: Alert!: Unable to access document. lynx: Can't access startfile http://localhost:443/ In the /var/log/apache-ssl/error.log I can see the following messages: [Fri Dec 25 22:52:56 1998] created shared memory segment #387 [Fri Dec 25 22:52:56 1998] Server configured -- resuming normal operations [Fri Dec 25 22:53:02 1998] SSL_Accept failed [Fri Dec 25 22:54:13 1998] SSL_Accept failed [Fri Dec 25 22:59:49 1998] SSL_Accept failed [Fri Dec 25 23:00:00 1998] SSL_Accept failed I've checked both possible combinations: 1) apache-common + apache-ssl (apache-common_1.2.6+1.16-3.deb + apache-ssl_1.2.6+1.16-3.deb) 2) apache + apache-ssl (apache_1.3.0-2.deb + apache-ssl_1.2.6+1.16-3.deb) - YES! the version numbers are different :-( Thanks for any help... Wojtek Zabolotny [EMAIL PROTECTED]
Problems with apache and postgres (already solved)
-BEGIN PGP SIGNED MESSAGE- Hi! Yesterday i upgraded some packages to Hamm frozen and has two problems. I don´t know if that where bugs or just my faults. Anyway, i solved them and maybe this information can help others. OK, here it goes: Number 1 Apache 1.3b5-2 I had to uncomment Port 80 in /etc/apache/httpd.conf. This was not nessary in previous versions of apache as it was the default port for ServerType standalone. Number 2 postgesql 6.3-2 Dpkg could not config postgresql due to problems in initdb. I tried to run initdb manually as user postgres from the postgres home dir /var/lib/postgres but this didn´t work because initdb could not find other programs (pg_id and postgres). After adding /usr/lib/postgresql/bin to PATH it worked. dpkg -configure worked also after that. Question: Is there a security problem when giving the user postgres a shell? Greetings, Ramin - E-Mail: [EMAIL PROTECTED] Date: 23-Mar-98 Time: 14:38:32 - -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBNRZs8PQ9+Dm4/+DZAQG5vgP+OgwHmLAGg1k5KxCNL15kbXced5rpLUGJ epCrMmQ278syHpdCIQfpJ04/7vxewIR/fYE7G6KvfhqoMp8s5pTJupFLqrImKRmo 68I7NPmWGblONY1aNUPzBF3pjPq1G/t2uERNf4RvBvNyPSndZWiLAK3BUhs65/Fs c/x9v4LqOuU= =Lb/9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with apache and postgres (already solved)
[EMAIL PROTECTED] wrote: Number 2 postgesql 6.3-2 Dpkg could not config postgresql due to problems in initdb. I tried to run initdb manually as user postgres from the postgres home dir /var/lib/postgre s but this didn´t work because initdb could not find other programs (pg_id and postgres). After adding /usr/lib/postgresql/bin to PATH it worked. dpkg -configure worked also after that. In the next release I name the whole path in the `su - postgres -c initdb ...' statement. The problem arises from the use of secure-su. Question: Is there a security problem when giving the user postgres a shell? Since root is not allowed to modify a PostgreSQL database, it is necessary for postgres to have a shell so that it is possible to run PostgreSQL administrative commands. Treat the postgres password with the same care as you would the root password. Alternatively, make it a no-login account so that only root can get to it (by `su - postgres'). -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP key from public servers; key ID 32B8FAA1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
DSELECT/DPKG Problems with Apache 1.1.3-6
Hello, I've been having problem with Apache 1.1.3-6 as supplied with Debian 1.3.1. Basically I've been using DSELECT, but reverted to DPKG in an effort to get more info on the problem. Alas, even the highest level of --debug failed to provide me with enough. A brief history: Apache 1.1.3-6 installed successfully Apache 1.1.3-6 uninstalled successfully Apache 1.2 installed successfully (Manually into /usr/local using the source from the Apache website). Apache 1.2 removed successfully (Had some problems I couldn't resolve) Apache 1.1.3-6 now won't install, despite successful a 'purge'. The interesting thing is that the version number is still visible in DSELECT even after 'purge'. On inspection, this is reflected in /var/lib/dpkg/status. Whether that is important or not I don't know. Has anyone encountered problems similar to this, or is there another switch that will point me in the right direction? . Or am I missing something really obvious? :-) Any help would be appreciated. I really don't fancy reinstalling the whole system :) Thanks in advance Nigel Price PS. Here's the most recent log with the debug options on. Start Log PC2154# dpkg --debug=3773 --install /cdrom/stable/binary/web/apache_1.1.3-6.deb D10: ensure_pathname_nonexisting `/var/lib/dpkg/tmp.ci' (Reading database ... 22370 files and directories currently installed.) Unpacking apache (from .../binary/web/apache_1.1.3-6.deb) ... D20: process_archive conffile `/etc/cron.daily/apache' no package, no hash D20: process_archive conffile `/etc/init.d/apache' no package, no hash D01: process_archive oldversionstatus=not installed conflictor=none D02: fork/exec /var/lib/dpkg/tmp.ci/preinst ( preinst install ) dpkg: error processing /cdrom/stable/binary/web/apache_1.1.3-6.deb (--install): subprocess pre-installation script returned error exit status 1 D02: fork/exec /var/lib/dpkg/tmp.ci/postrm ( postrm abort-install ) D10: ensure_pathname_nonexisting `/var/lib/dpkg/tmp.ci' D10: ensure_pathname_nonexisting running rm -rf D10: ensure_pathname_nonexisting `/var/lib/dpkg/reassemble.deb' Errors were encountered while processing: /cdrom/stable/binary/web/apache_1.1.3-6.deb PC2154# End Log -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: DSELECT/DPKG Problems with Apache 1.1.3-6
The pre-install script in that package is failing - it says returning status 1, and it should return 0. You can use dpkg to extract the package archive, and then try to run DEBIAN/preinst by hand. That should let you figure out what is wrong with the script. Sometimes it is something simple like the interpreter does not exist (the file mentioned after the #! on the first line) or there's no exit statement at the end of the script. Sometimes the script runs another program that fails or doesn't exist. Bruce -- Can you get your operating system fixed when you need it? Linux - the supportable operating system. http://www.debian.org/support.html Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
