I'm in need of a bit of assistance from you Debian users. I have two servers that I thought were identical installations, both running Debian Lenny. Tonight I started the upgrade to Squeeze on both servers and one of them went smooth. The other one started out good but fails on the postconfiguration of openssh-server. I'm getting the following message:
I have just been told that httpd was not running on my Centos virtual server. It seems that my hosting company rebooted my server 2 days ago and that httpd restart failed due to:
Starting httpd: httpd: Syntax error on line 213 of /etc/httpd/conf/httpd.conf: Syntax error on line 2 of /etc/httpd/conf.d/proxy_ajp.conf: Cannot load /etc/httpd/modules/mod_proxy_ajp.so into server: /etc/httpd/modules/mod_proxy_ajp.so: undefined symbol: proxy_module
I had worked around and forgotten about this some time ago. The problem arose because the most recent httpd update installed proxy_ajp.conf into /etc/httpd/conf.d which was then loaded on restart The trouble is I do not use mod_proxy (I think just to try and get a lean and mean web server) and proxy_ajp.conf does not check if mod_proxy is loaded before it tries to LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
Hence httpd fails to restart. RedHats's bug tracker lists this as an old issue (which was never resolved) [URL] My workaround was to rename proxy_ajp.conf to proxy_ajp.conf.orig so that httpd would start up correctly. However any updates simply reinstall proxy_ajp.conf and so IMO the problem needs to be resolved at source. how to ensure that httpd updates do not bite me in the future? Do I really have to run mod_proxy whether or not I need it?
I have squeeze using the default setup with 5 seperate partitions on hard drive. All other updates are fine but it will not install the Linux-Image-2.6.32-5-amd64. I get message that not enough room. I think this is the kernal update. I use update manager. Is there a fix for this short of resizing the partition. This is a one computer/user setup. I had this problem on a previous install of stable and ignored it thinking that it was a glitch. That install was an experimental setup and I liked it but it didn't work on the internet very well so went to testing.
I have an old computer a friend of mine found in a dumpster, and I've decided to use it as a file server. After finally getting it to connect to my wifi network, I tried connecting to it via OpenSSH on my main desktop. After I connected, I noticed OpenSSH was being very laggy. Whenever I type anything in there's a very noticable and annoying delay from when I type it to when it appears on screen. Now, a while ago a friend of mine was helping me fix my laptop when fglrx drivers broke x, and I set up openssh on there so he could access it. According to him, there was no lag (and he's half-way across the globe, whereas my file server is in the other room). The computer is an old Pentium 4 with one and a half gigs of RAM, two hard drives (one I use for the os/swapping and the other I use for /home). It's connected to wifi via a spare USB Linksys 802.11 bg adaptor I found lying around, and it's using the default drivers that come with Debian to connect.
I have VNC working but I like how freenx starts in it's own session. It is handy for when my account is not logged into the server and VNC hasn't started.I have freenx working but it requires sshd_config to enable PasswordAuthentication. This isn't a major security problem at the moment since I have deny.hosts running but I still don't like it enabled. I would much rather only use the keys.
On a Debian 5.0.8 I have a problem with OpenSSH server (sshd): when connecting to it from another host there is always a 10 seconds delay before sshd gives login prompt to the client. After the connection is established the communication goes on without any interruption. This long delay started to happen a few months ago and sshd_config was not changed at that time.
Here is a short description of the conversation between the putty client (on MS Windows) and sshd: - putty client starts connection to sshd - 10 s delay - sshd returns "login as:" - user types username in putty window - sshd returns "password:" - user types password in putty window - sshd returns MotD and shell prompt
Here is a short description of the conversation between the OpenSSH client (on a Debian 6) and sshd: - client does "ssh email@example.com" - 10 s delay - sshd returns "Password:" - user types password - sshd returns MotD and shell prompt
I tried connecting from: - local host - NO DELAY - a host on the same subnet - delay exists - a host on another subnet - delay exists
I've found the following suggestions but to no avail (of course I restarted sshd after changing its configuration): - on server put "UseDNS no" at the end of /etc/ssh/sshd_config - in /etc/hosts on the server define mappings between IP addresses and host names for the ssh clients - on client use "GSSAPIAuthentication no" in /etc/ssh/ssh_config
I have a issue that could get me fired, so I would appreciate your input. My knowledge about linux is limited The company I work for has a Dell Poweredge 6850 that keeps pretty much everything (databases, websites, etc). The server had a Virtual Drive created from 2 Physical Drives. Since the HDD space was getting low, we got a new drive, inserted it, formatted and rebooted the system. But the system now refuses to start, giving an FAILED message, something related to EXT2 partition that cannot be read at /dev/hda1
I have a small problem on my Compaq Evo Centos 5.4 web server. The web server runs just fine, the problem is it fails to restart from a power outage. Simple edit the BIOS. No! For a reason I can't think of the keyboard stops working after a few key strokes following the F10 to enter BIOS setup. Then its a power cycle. If left to BOOT the PC and keyboard are fine. After hearing about viruses which get to the BIOS I will ask can NIX get that far so I can adjust the Power ON?
My system is a three days old Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) with an Intel(R) Core(TM) i7 CPU 60 @ 2.80GHz. It does start, goes through the grub and then spits out strange messages and just freezes before the KDE can be started. I have to restart again, until it really boots everything. This is happening in a random pattern.
I activated bootlog, but as far as I can see, the log only tracks, if the system is really booting. So I also have the dmesg copied into pastebin. These are the only two logs I know, now.
The code of the boot log goes here- Wed Aug 17 10:24:19 2011: Setting parameters of disc: (none). Wed Aug 17 10:24:19 2011: Setting preliminary keymap...done. Wed Aug 17 10:24:19 2011: Activating swap...done.
Some problems keep bothering me and dont let me use my debian sqeeze with joy.Im in network with no DHCP on. When installing i didnt configure my eth network card.After each restart i need to configure manually my eth because it loses it.
I'm using Debian 8 and I have ipset v6.23 and iptables v1.4.21. I put a rule with ipset in rules.v4 file and then I restart the iptables with netfilter-persistent service. When I reboot the iptables list is empty. But if in the file I don't put a rule with ipset, after reboot the iptables list is correct.
Sometimes when we update/upgrade packages we get the restart required icon on the desktop panel which means we need to reboot for the update to complete. Is there someway to know which or what package required the reboot to happen ?
in configuring a fresh install of Squeeze. I discovered that it is possible to power off the system under gnome simply by pressing the power button or by selecting the "Shut Down" entry on "System" menu.However I need to restrict this option only to root. How can I do that?
I just setup Ubuntu 10.04, and immediately installed OpenSSH using synaptic. I edited the /etc/ssh/sshd_config file e.g. no password authentication, non-standard port, etc. Using /etc/init.d/ssh restart I restarted the daemon, and everything worked perfectly. However, now it's almost like there is a lock on my service somehow. I edited the config file and added "PrintMotd no" and "Banner none". I killed all my active ssh sessions, restarted, and still saw the motd and the banner.
I then tried sudo /etc/init.d/ssh stop. The script reported ok, but netstat reported sshd as still listening on the port I had defined. I could still login. At this point, I don't know what else to do. I have tried looking at auth.log, I don't see anything funny there. I tried rebooting, and the config changes are (apparently) not loaded, I still see the motd upon ssh login. This is a totally clean system so I don't know what I am doing improperly.
I installed the latest Debian on a computer to make a backup appliance. No GUI.When the computer starts, everything is okay. The DHCP client is running, the network interface have an address, fine.If I do a /etc/init.d/network restart (or stop + start), no more DHCP client. t is stopped when the interface is down. When the interface is up, I have to start it manually.1 - is it normal ?2 - isn't ifup's job to launch the dhcp client ?3 - can /etc/network/if-up.d be the right place to resolve this ?
I am having slight issue with setting up file sharing. I have a windows 7 pc and hp proliant microserver running. I have a raid array which I am using as a share for storing music, pictures etc. When I reboot the debian server I can't connect to the server from the windows 7 PC (I have mapped a network drive) until I go on to the server and restart samba with /etc/init.d/samba restart - then everything works fine. I can ping the server with both ip and hostname but the network drive does not connect - this is straight after a reboot. Is the /etc/init.d/samba restart doing something differently to when the server boots? I have read several posts relating to printer sharing issues which point to samba not starting before cups so I am wondering if samba is starting before some of the relevant networking services.
I use Ubuntu 8.04 Server It uses OPENSSH 4.7 version I want to upgrade from OPENSSH 4.7 to OPENSSH 5.5 [URL]..Other Ubuntu releases have updated package Can I use this one The Maverick Meerkat OpenSSH 5.5p1-4ubuntu1
I have two Debian 5 servers which running on both the same version of OpenSSH (5.1p1) and OpenSSL (0.9.8g).
One week ago, I set ssh keys on both of them and create the file "authorized_keys". I was able to connect on each server via SSH without password (which is the purpose of ssh keys) but I had an issue with the SSH service and I had to restart one of my server. And since this time, when I try to connect to my other server with the same ssh command, the command ask me to type the password...
This is the result of the ssh command (with the argument -v):
Code: OpenSSH_5.1p1 Debian-5, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to MY_SERVER [184.108.40.206] port 22. debug1: Connection established.
I've just installed lenny from dvd, and am just settling in. I'm curious about virtual machines. so I've installed xen. With xen comes qemu by default. Now the setup I've recently become familiar with is Suse-11 which is quite slick.In Suse, Yast provides a distribution prepared virtual management section for xen, including an installer. Debian's setup is similar but not a clone. I want to try out the installer. Aside from the differences, debian has a screaming deficit. On booting dom0 in Lenny, if fails to get into gnome, badly. I can tell what's probably wrong, but I need to fix it. Now I'm also a gentoo fan and very practised at posting queries, so here goes.
Debian's config for X is somewhat unhelpful. The xorg.conf just states Configured device and configured monitor for its components. If it expanded on just what the settings were it would help. What I have is a frambuffer driver not loadinf or being implemented.