[opensuse] Newbie has problems installing 12.1 with LAMP
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. Twice now I have tried installing OpenSuse 12.1 on a clean partition (formatted as part of install, containing both / and /home) Everything goes well, I install nvidia propriety driver and firmware for tv card which kaffine operates well. I do a full update through yast. I am using KDE. The problem happens when I install the Lamp-server packages/patten. This seems to go OK, but the services are not turned, so I go through Yast and activate apache2 and mySql. I can now browse web pages at 127.0.0.1, including a sample php page I created. The problem happens when I next reboot. When I log on I get a dialog box saying: "Warning: Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file of directory" I can log on, but functionality is limited, eg network, internet or dvb card. Google suggests I should edit my /etc/rc.conf file, but my system does not have one (I don't think it is part of OpenSuse 12.1) I have had a look through the documentation etc and cannot find anything to help me. Can someone suggest what I should do to restore my system? ~If I have failed in finding some direction on this problem, can you please point me at the article and tell me how my search skills failed! With Thanks, HDixon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
hugh wrote:
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. Twice now I have tried installing OpenSuse 12.1 on a clean partition (formatted as part of install, containing both / and /home) Everything goes well, I install nvidia propriety driver and firmware for tv card which kaffine operates well. I do a full update through yast. I am using KDE.
The problem happens when I install the Lamp-server packages/patten.
This seems to go OK, but the services are not turned, so I go through Yast and activate apache2 and mySql. I can now browse web pages at 127.0.0.1, including a sample php page I created. The problem happens when I next reboot. When I log on I get a dialog box saying:
"Warning: Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file of directory"
I'm not sure, but I think you can safely ignore that.
I can log on, but functionality is limited, eg network, internet or dvb card.
You're saying your network was not started? -- Per Jessen, Zürich (3.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 30 December 2011 19:58:54 Per Jessen wrote:
hugh wrote:
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. --snip-- "Warning: Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file of directory"
I'm not sure, but I think you can safely ignore that.
I can log on, but functionality is limited, eg network, internet or dvb card.
You're saying your network was not started?
yes, in part. I have had a look at a number of services. They are not getting started at boot. I can start them through Yast and functionality returns. Can you tell me how through yast to set the service so that it starts at boot, so I do not have to restart them every time I restart the machine? (I suspect this question is a failure on my part to google correctly. A link to an article on the service controller in yast would be excellent if there is one.) The other part of my response is that I am getting a message "KDE daemon failed, Kdeinit4 segfault(11)" I also get a message "default audio system does not work using default instead" The audio system is dead. I am unsure if the premature death of kdeinit4 will result in other problems.... Thankyou for the help so far! HDixon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
hugh wrote:
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. Welcome! :)
Can you tell me how through yast to set the service so that it starts at boot, so I do not have to restart them every time I restart the machine?
Have a look under YaST > System > System services (runlevel) or if you are running services through xinetd, Yast > Network services > Network services (xinetd) Should be fairly self-explanatory from there. (n.b., I'm translating back from openSUSE running in Dutch, so labels might be slightly different) Good luck! Haro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/30/2011 07:21 AM, Haro de Grauw pecked at the keyboard and wrote:
hugh wrote:
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. Welcome! :)
Can you tell me how through yast to set the service so that it starts at boot, so I do not have to restart them every time I restart the machine?
Have a look under YaST > System > System services (runlevel)
This is the proper place. Select "expert" mode so you can see where to select the run levels to turn on.
or if you are running services through xinetd,
Yast > Network services > Network services (xinetd)
Should be fairly self-explanatory from there.
(n.b., I'm translating back from openSUSE running in Dutch, so labels might be slightly different)
Good luck! Haro
-- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/12/11 12:05, hugh wrote:
On Friday 30 December 2011 19:58:54 Per Jessen wrote:
hugh wrote:
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. --snip-- "Warning: Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file of directory"
I'm not sure, but I think you can safely ignore that.
I can log on, but functionality is limited, eg network, internet or dvb card.
You're saying your network was not started?
yes, in part. I have had a look at a number of services. They are not getting started at boot. I can start them through Yast and functionality returns. Can you tell me how through yast to set the service so that it starts at boot, so I do not have to restart them every time I restart the machine? (I suspect this question is a failure on my part to google correctly. A link to an article on the service controller in yast would be excellent if there is one.)
I don't know where you're looking in YaST, but System > System Services (Runlevel) seems to do the job :) Bob -- Bob Williams System: Linux 2.6.37.6-0.9-desktop Distro: openSUSE 11.4 (x86_64) with KDE Development Platform: 4.7.2 (4.7.2) Uptime: 06:00am up 15:39, 4 users, load average: 0.11, 0.13, 0.24 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
hugh <hdixon@bigpond.net.au> wrote:
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. Twice now I have tried installing OpenSuse 12.1 on a clean partition (formatted as part of install, containing both / and /home) Everything goes well, I install nvidia propriety driver and firmware for tv card which kaffine operates well. I do a full update through yast. I am using KDE.
The problem happens when I install the Lamp-server packages/patten.
This seems to go OK, but the services are not turned, so I go through Yast and activate apache2 and mySql. I can now browse web pages at 127.0.0.1, including a sample php page I created. The problem happens when I next reboot. When I log on I get a dialog box saying:
"Warning: Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file of directory"
I can log on, but functionality is limited, eg network, internet or dvb card.
Google suggests I should edit my /etc/rc.conf file, but my system does not have one (I don't think it is part of OpenSuse 12.1)
I have had a look through the documentation etc and cannot find anything to help me. Can someone suggest what I should do to restore my system?
~If I have failed in finding some direction on this problem, can you please point me at the article and tell me how my search skills failed!
Hugh, Do yourself a big favor and change init systems from systemd to sysvinit. I don't recall the exact command to do this but its in the 12.1 release notes. Fyi: systemd is new to opensuse in 12.1. It seems okay for a basic desktop, but not for a newbie running a lamp server. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Dec 30, 2011 at 8:41 AM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
hugh <hdixon@bigpond.net.au> wrote:
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. Twice now I have tried installing OpenSuse 12.1 on a clean partition (formatted as part of install, containing both / and /home) Everything goes well, I install nvidia propriety driver and firmware for tv card which kaffine operates well. I do a full update through yast. I am using KDE.
The problem happens when I install the Lamp-server packages/patten.
This seems to go OK, but the services are not turned, so I go through Yast and activate apache2 and mySql. I can now browse web pages at 127.0.0.1, including a sample php page I created. The problem happens when I next reboot. When I log on I get a dialog box saying:
"Warning: Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file of directory"
I can log on, but functionality is limited, eg network, internet or dvb card.
Google suggests I should edit my /etc/rc.conf file, but my system does not have one (I don't think it is part of OpenSuse 12.1)
I have had a look through the documentation etc and cannot find anything to help me. Can someone suggest what I should do to restore my system?
~If I have failed in finding some direction on this problem, can you please point me at the article and tell me how my search skills failed!
Hugh,
Do yourself a big favor and change init systems from systemd to sysvinit.
I don't recall the exact command to do this but its in the 12.1 release notes.
Fyi: systemd is new to opensuse in 12.1. It seems okay for a basic desktop, but not for a newbie running a lamp server.
Greg
Per the release notes: == Booting with systemd or sysvinit By default, openSUSE now boots using systemd. In case of trouble, you can switch back to the old way using sysvinit by pressing the F5 key on the boot. If you want to switch to sysvinit permanently, install the sysvinit-init package. To switch back to systemd, reinstall the systemd-sysvinit package. == Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 30 December 2011 17:51:43 hugh wrote:
Hi, I am new to OpenSUSE, but have come from a different Linux Distro. Twice now I have tried installing OpenSuse 12.1 on a clean partition (formatted as part of install, containing both / and /home) --snip--
~If I have failed in finding some direction on this problem, can you please point me at the article and tell me how my search skills failed!
With Thanks, HDixon
Thankyou all for the assistance and encouragement. My system is now working well. A run down on what I did: Booting with systemV using the F5 key was really easy once I knew to do it, and a lot of the warning messages etc disappeared. Thankyou Greg! Prior to your responses I had been using "YaST > System > System services (runlevel)". I had already found that the enable/disable buttons start and stop the services, however for me it was not saving the service states for the next time I booted. I found that the "OK" button makes the changes permanent, while "CANCEL" makes them apply only to the current session. **Being nervous and unsure I had been pressing CANCEL here** This was causing many of my reboot problems! In "YaST>network devices>network settings>global" I selected "User controlled with Ntetwork Manager" and the networking was good again Finally the sound was a problem. I installed the pulseaudio tools and found that pulse audio had been set to mute. I turned pulse audio back on and it was good. Is there anywhere else in the GUI I could have done this? It seems a bit major to me that I have to find and install a package to deal with something as rudimentary as this... I am hoping this can get back to the developers etc as a use case to consider for future versions! HDixon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Bob Williams -
Greg Freemyer -
Haro de Grauw -
hugh -
Ken Schneider - openSUSE -
Per Jessen