Can I just move the hard drive to another box? If so, how? beside the obvious... unplug, remove, install, plug in! I have SuSe 10.1 with ISPConfig loaded on a SATA drive. I tried it just to see if it would work and it would not... the only error I could see in the checks was that ispconfig.http could not resolve the FQDN then it would just go to text screen log in.
If the new system has the same IP address as the old one and you plug in the HDD on the same controller, then there should be no problem. If the IP address has changed, take a look here: http://www.howtoforge.com/forums/showthread.php?t=2760
Controller being the same as network/router etc... ? The IP crossed my mind this morning and I was going to try that again today. I did not change the internal IP address before I tried it yesterday. e.g. the HDD was on 192.168.2.5 and the machine I put it in and tried was 192.168.2.2. Thanks, I'll let you know if I was successful. Well... that didn't work! I went in and changed the IP of the box I am wanting to use to what is listed for ISPConfig and the sites. Restarted then shut it down. Disconnected the current drive which is WinXP and placed in the Linux drive the restarted again. Still taking me to a text login screen. Just out of curiosity could it be that it is actually working but no in GUI mode!? huh... let me test that... Wish I would think of these things before I restore back to the old box! No... it just is not booting up to the Linux HDD for some reason. Interesting because the mobo's are the same but there is a huge difference in cpu and memory.
No, I mean the controller where you plug in the HDD on the new system. For example, if your HDD was /dev/hda on the old system, and you use the wrong controller on the new system, it might be recognized as /dev/hdc there instead of /dev/hda.
Got it... how would I find that out? The new system has never had a Linux designation such as /hda or /hdc and the mother boards are both the same and I am even using the same Sata connector on the board. When I do try to boot to the Linux drive in the new system it goes to a text login (system login screen. I can login as root from there, is there a way I can check or change it from there? I will start researching Linux commands also and see what I can dig up... and check the BIOs and see what I can do from there. Final option is to do a clean install but how difficult is it to transfer all the ISPConfig data, domains, sites, users over to the new drive? Would it be as easy as copying specific folders over?
Run Code: fdisk -l or Code: df -h Take a look here: http://www.howtoforge.com/forums/showthread.php?t=2717&highlight=moving+ispconfig
okay... I ran df -h on the drive in the old system, then in the new system. Both results were the same; /dev/sda3 udev /dev/sda1 I can't help but feel it is a hardware issue between the 2 boxes, maybe graphics card or something. Seems to work fine in the new box it just boots to a text screen which might be okay if I was a linux command wizzard but I am a GUI baby. I am probably going to do a fresh install since I do have a couple HDDs hanging around and follow the link you gave me for moving settings and such. If I use opensuse 10.2 (current setup is on 10.1) do you think there will be any issues?
Some people reported that PHP files weren't shown correctly by Apache on OpenSuSE 10.2, although it worked for me.
thanks... I had a successful install of 10.2 and ISPConfig so now I am off to go back to the link you gave me for moving over stuff.
I do seem to have this problem now... I got everything transferred over and running off the new server but when I go to any of the pages I host that have links to PHP pages (guestbook, gallery) and click on the link it asks if I want to "Open with; or save to disk". I do recall there was a problem with one module failing to load during installation. However, it appered to be the same problem as with previous suse versions, a "duplicate" rpm, and I clicked "Ignore" and proceeded with the download and install. I did some research and could find no issues regarding 10.2/Apache2/PHP. I did for Enterprise but it is using Apache?Tomcat. It mentions installing another program... see this PHP . I also double checked /etc/sysconfig/apache2 because during set-up we modify this adding "rewrite" and all seems to be well there. Thoughts, suggestions... ?
Don't use SuSE! Take a look here: http://www.howtoforge.com/forums/showthread.php?t=9778&highlight=opensuse+10.2+php
I took a look and followed what the other guy did and I still had no luck. "Don't use SuSe!" What would be your recommendations for a small home server?
Just in case here is some stuff that I think might help trace the problem... apache access log entires for php page Code: 192.168.2.4 - - [04/Feb/2007:09:22:16 -0500] "GET /guestbook/index.php HTTP/1.1" 200 25194 "http://www.heartwinds.org" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)" 192.168.2.4 - - [04/Feb/2007:09:22:33 -0500] "GET /guestbook/index.php HTTP/1.1" 304 - "http://www.heartwinds.org" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)" 192.168.2.4 - - [04/Feb/2007:09:22:40 -0500] "GET /guestbook/index.php HTTP/1.1" 304 - "http://www.heartwinds.org" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)" apache error log Code: [Sun Feb 04 00:42:02 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 00:42:02 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 01:21:13 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 01:21:13 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 01:28:53 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 01:28:53 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 01:30:08 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 01:30:08 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 01:30:08 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 01:30:08 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 03:34:31 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 03:34:31 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:39:26 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:39:26 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:43:20 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:43:20 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:43:28 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:43:28 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:54:44 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:54:44 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 05:59:38 2007] [error] [client ::1] Directory index forbidden by Options directive: /srv/www/htdocs/ [Sun Feb 04 05:59:39 2007] [error] [client ::1] Directory index forbidden by Options directive: /srv/www/htdocs/ [Sun Feb 04 06:02:00 2007] [error] [client ::1] Directory index forbidden by Options directive: /srv/www/htdocs/ [Sun Feb 04 06:02:01 2007] [error] [client ::1] Directory index forbidden by Options directive: /srv/www/htdocs/ [Sun Feb 04 06:02:09 2007] [error] [client ::1] Directory index forbidden by Options directive: /srv/www/htdocs/ [Sun Feb 04 06:35:48 2007] [error] [client ::1] Directory index forbidden by Options directive: /srv/www/htdocs/ [Sun Feb 04 06:35:49 2007] [error] [client ::1] Directory index forbidden by Options directive: /srv/www/htdocs/ [Sun Feb 04 06:35:50 2007] [error] [client ::1] Directory index forbidden by Options directive: /srv/www/htdocs/ [Sun Feb 04 07:45:56 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 07:45:56 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 08:30:24 2007] [notice] caught SIGTERM, shutting down [Sun Feb 04 08:30:24 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2) [Sun Feb 04 08:30:25 2007] [notice] Apache/2.2.3 (Linux/SUSE) configured -- resuming normal operations [Sun Feb 04 08:31:39 2007] [notice] caught SIGTERM, shutting down [Sun Feb 04 08:31:39 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2) [Sun Feb 04 08:31:40 2007] [notice] Apache/2.2.3 (Linux/SUSE) configured -- resuming normal operations [Sun Feb 04 08:39:01 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 08:39:01 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 08:46:01 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 08:46:01 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 08:57:47 2007] [notice] caught SIGTERM, shutting down [Sun Feb 04 08:57:48 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2) [Sun Feb 04 08:57:48 2007] [notice] Apache/2.2.3 (Linux/SUSE) configured -- resuming normal operations [Sun Feb 04 08:59:02 2007] [notice] caught SIGTERM, shutting down [Sun Feb 04 08:59:03 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2) [Sun Feb 04 08:59:03 2007] [notice] Apache/2.2.3 (Linux/SUSE) configured -- resuming normal operations [Sun Feb 04 09:00:55 2007] [notice] caught SIGTERM, shutting down [Sun Feb 04 09:00:55 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2) [Sun Feb 04 09:00:55 2007] [notice] Apache/2.2.3 (Linux/SUSE) configured -- resuming normal operations [Sun Feb 04 09:02:47 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 09:02:47 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 09:10:04 2007] [notice] caught SIGTERM, shutting down [Sun Feb 04 09:10:05 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2) [Sun Feb 04 09:10:05 2007] [notice] Apache/2.2.3 (Linux/SUSE) configured -- resuming normal operations [Sun Feb 04 09:22:16 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 09:22:16 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 09:22:33 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 09:22:33 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 09:22:40 2007] [error] an unknown filter was not added: PHP [Sun Feb 04 09:22:40 2007] [error] an unknown filter was not added: PHP httpd -t Code: server:~ # httpd -t Syntax OK server:~ # I also found this PHP tied it and got this Code: server:~ # /etc/init.d/apache2 restart httpd2-prefork: Syntax error on line 175 of /etc/apache2/httpd.conf: Cannot load /srv/www/modules/mod_php.so into server: /srv/www/modules/mod_php.so: cannot op en shared object file: No such file or directory and these are all the locations of config_inc_php which seem to be a lot! Code: home/admispconfig/ispconfig/lib/config.inc.php root/ispconfig/scripts/lib/config.inc.php srv/www/htdocs/phpMyAdmin/config.inc.php srv/www/htdocs/phpMyAdmin/config/config.inc.php srv/www/web2/web/gallery/include/config.inc.php srv/www/web2/web/gallery/include/config.inc.php srv/www/web2/web/gallery/include/config.inc.php srv/www_orig/htdocs/phpMyAdmin/libraries/config.inc.php As I said before I tried the items in the last link you gave me and that did not work so I returned all the files back their content before trying the changes.
Take a look here: http://www.howtoforge.com/forums/showthread.php?t=4770&highlight=$go_info["server"]["apache2_php"]
Actually I had looked at that a long time ago when I first noticed the PHP filter errors on the log. Up until a clean (and new) install of suse10.2 any php content worked so I did not fix what was technically not broken... Yesterday I reverted back to the old box and server setup pending figuring this out. Would the fact that the new box I want to use has a hyper-thread processor in it matter (to linux)? Suse... seems not to be a favored OS for yourself and Till. Having the opportunity to setup a new box any way I want what would you recommend? Based on what I have seen and read in the forum here Debian seems to present the least amount of problems and less frequent updates which to me would seem to make it more stable than say Fedora or Suse.
No. I recommend Debian. If that doesn't work (because your hardware requires new drivers, etc.), try Ubuntu, it's based on Debian, but has newer drivers.
Thanks! I downloaded the 2 Debian DVD ISOs and will see how it goes. I plan to follow your Perfect Setup and shouldn't have to much problem even though you cite a NetInstall in that HowTo. I'll let you know how it goes!
Sarge or Woody? I did a Debian Sarge NetInstall and ran into 2 problems... I tried installing the linux26 kernel as cited in the HowTo but then the system freezes up when it is trying to detect the cd-rom so I tried again without entering linx26 and it went fine. My second problem is the mouse. Being GUI dependent I checked Desktop Environment with Mail Server. I can't seem to get the mouse recognized... I used /dev/ttyS0 and it asked me the mouse type (Logitech) but still no deal. It is a KVM setup that is USB and 2 6-pin lines that branch off for keyboard and mouse. Never had to manually configure a mouse before! Any ideas on either? as of 9:10pm EST... I have worked the Debian Sarge HowTo up to installing Apache. Long day so I am going to rest my mind before hitting the sack. After I installed quota and edited /etc/fstab I got this Code: xlib: connection to 0.0 refused by server xlib: no protocol specified and it repeats that 2 more times before it returns to command line. ? I think my mouse issue is a optical mouse... I will have to dig later to see if I can set it up to use it but feel free to provide an answer if you know it!
I also had this problem with my laptop. When I took out the mouse and put it in again while the system is running. It found the mouse and worked. (This was a USB mouse.)
Hi Jorem, Thanks for replying. That did not solve the problem for me but it did set my brain in motion! First I dug around for a mouse with a tail and it seems I have none anymore! Then I realized the mouse I am using on my KVM setup is not only wireless but optical also. I plugged a wireless ball mouse into the system I am setting up, rebooted and it works. So it appears to be the wireless optical mouse that is not being read by the system. Unless someone knows a resolution I'll have to dig for an answer after I get the setup finished. Thanks again, Lance
