Topic: No Access to my SME-Server

[CharlieBrady]

Something strange happened. I installed the Printer Queue admin on my machine. In the server-manager I found no further informations. Then I tried thru a Webbrowser to access the admin; and it worked! I was able to log in to the Queue admin and analyze my printer.

But the rest is the same …

Your information is confusing and conflicting. I think you are saying that previously you could not access server-manager, but now you can access server-manager. You say "the rest is the same". Please make a list of "the rest". What is working and what is not working? For those which are not working, specify exactly what you mean by "not working".

[lucaegloff]

you missed my request

Yes, I try to type the command, but I can't get the character which comes after history … Although it is on the keyboard and I have the right layout installed.

[Stefano]

any further info (i.e. language and keyboard layout)?

[lucaegloff]

Your information is confusing and conflicting. I think you are saying that previously you could not access server-manager, but now you can access server-manager. You say "the rest is the same". Please make a list of "the rest". What is working and what is not working? For those which are not working, specify exactly what you mean by "not working".

As I wrote before, I can log in to the server-manager, text-based on the Server console. But I can not reach the server-manager thru a Webbrowser on another machine in the local Network.
On the Server I can log in and do what I want (or can). Every Service seems to run - except the https-e-smith, but there I'm not sure … see above.
From another machine in the local Network or over Internet, I can not log in to the server-manager, nor to the SOGo Interface. I was not able to log in via ssh. But I get the index-page of the Webserver (under construction! I have no site running there)

Hope all this was clear

[lucaegloff]

any further info (i.e. language and keyboard layout)?

Language: german
Keyboard: de_CH-latin1

[Stefano]

a fast research with google gives me this

On some keyboards the pipe is hard to find. On a US 101 keyboard the pipe should be available via Shift-\ ("backslash"). On a German keyboard it is on the left together with < and > and the Alt Gr modifier key must be pressed to get the pipe.

be aware that this could not work if you are using a virtual machine (google will tell you more)

[lucaegloff]

a fast research with google gives me this

be aware that this could not work if you are using a virtual machine (google will tell you more)

Sorry, none of this works

[janet]

lucaegloff

Is remote access to server manager & ssh enabled in server manager panels ?
By default they are disabled.
Check using the text based server manager.

As you can access the text based server manager & command line locally on the server or from the local network, then external access appears to be your problem.
What app are you using on a workstation to access ssh on the server, Putty ?

If you can ssh from a workstation to server using Putty, then you can paste commands directly, & copy screen output using the little icon in the top left corner, so if you are not using Putty, then I suggest you install it on your workstation (& configure it correctly).

Are you sure you did not upgrade Sogo or make config changes to Sogo recently ?

Sogo is probably the source of your problems

I suggest you Google your Sogo error message
[Warn] worker http://127.0.0.1:20000/SOGo/dav is already in use by another worker

It seems this is a common problem, but I'm not sure of your exact issue. I don't use Sogo so cannot help.

[janet]

lucaegloff

If I could print out the log files, it would be easier for me

You can view & filter the log files using the (text based) server-manager, View log files panel.
You can Download them too, & then print them if required.

Alternatively do
cat /var/log/messages >> /home/e-smith/files/ibays/ibayname/html/messages20140228.txt

(replace log filename (messages) & output location (ibayname) & filename (messages20140-228.txt) as required)

Then read in a browser or Notepad etc & print if required.
You may need to change ownership permissions on those saved log files

[janet]

lucaegloff

cd /service/httpd-e-smith
sv d .
./run

Charlie asked you to type
cd /service/httpd-e-smith
sv d $PWD
./run

(although he may have edited/corrected his post)

If httpd-e-smith is not running, which you say is not running, then you will not be able to access server manager.

Enable it using
service httpd-e-smith start

(although the earlier command given should have started it)
Check status (ie is it running) again
service httpd-e-smith status

& show us the output rather than just saying it's running, you can write it down easily.

Then try accessing server manager again, assuming of course you have Remote access enabled from specific IPs in the server manager panel (if accessing remotely).

[lucaegloff]

lucaegloff

Is remote access to server manager & ssh enabled in server manager panels ?     Yes
By default they are disabled.
Check using the text based server manager.   Did It

As you can access the text based server manager & command line locally on the server or from the local network, then external access appears to be your problem.   Right
What app are you using on a workstation to access ssh on the server, Putty ? No. I use Terminal (On Mac OS X)

If you can ssh from a workstation to server I can not, as I wrote earlier using Putty, then you can paste commands directly, & copy screen output using the little icon in the top left corner, so if you are not using Putty, then I suggest you install it on your workstation (& configure it correctly).

Are you sure you did not upgrade Sogo or make config changes to Sogo recently ? The last update before the problems appeared, I made one month ago. I did the last update, after the problems emerged

Sogo is probably the source of your problems

I suggest you Google your Sogo error message
[Warn] worker http://127.0.0.1:20000/SOGo/dav is already in use by another worker

It seems this is a common problem, but I'm not sure of your exact issue. I don't use Sogo so cannot help. I googled the Problem. It appears often on forums, but It seems not to be a problem, normally. I'm on ...

[lucaegloff]

lucaegloff

You can view & filter the log files using the (text based) server-manager, View log files panel. Yes, I mentioned above, what I found in the log files. But I will try to filter this logs better an search more specific
You can Download them too, & then print them if required.

Alternatively do
cat /var/log/messages >> /home/e-smith/files/ibays/ibayname/html/messages20140228.txt

(replace log filename (messages) & output location (ibayname) & filename (messages20140-228.txt) as required)
This is a very clever trick. Thanks. I have to install an iBay before, cause I have none till now.
Then read in a browser or Notepad etc & print if required.
You may need to change ownership permissions on those saved log files  Will tell you…  Thanks

[lucaegloff]

lucaegloff

Charlie asked you to type
cd /service/httpd-e-smith
sv d $PWD
./run

(although he may have edited/corrected his post)

If httpd-e-smith is not running, which you say is not running, then you will not be able to access server manager. I messed up. Sorry! It is running. The status shows: run: /service/httpd-e-smith: (pid 3601) 106s, normally down) - I just restarted the server.


Enable it using
service httpd-e-smith start

(although the earlier command given should have started it)
Check status (ie is it running) again
service httpd-e-smith status

& show us the output rather than just saying it's running, you can write it down easily.

Then try accessing server manager again, assuming of course you have Remote access enabled from specific IPs in the server manager panel (if accessing remotely). Remote access is granted. No access!

[lucaegloff]

Hi to all

I was able to generate some files with the logs. I redirected to a file and then put with ftp to another Linux machine I have …
The Pipe seems not to work. All other characters are no problem … I took the broken Pipe and this worked like the Pipe.

@Stefano - The history you asked:

   25  yum install smeserver-sogo --enablerepo=nethsme --enablerepo=sogo
   26  yum install memcached
   30  yum install memcached.i386
   34  yum install smeserver-sogo --enablerepo=nethsme --enablerepo=sogo
  137  yum install make
  191  yum install smeserver-print-monitor --enablerepo=smecontribs


The log of the sshd is simple:

@40000000530de5ec23281194 Received SIGHUP; restarting.
@40000000530de5ec23281964 Server listening on 192.168.1.44 port 22.
@40000000530f1d551e1e904c Received signal 15; terminating.
@40000000530f1de32b93b93c Server listening on 192.168.1.44 port 22.
@40000000530f65ce050047f4 Server listening on 192.168.1.44 port 22.
@40000000530f6a5b06d8b55c Server listening on 192.168.1.44 port 22.
@40000000530f79dc37f5dfd4 Received signal 15; terminating.
@4000000053103e4e1d6c8dfc Server listening on 192.168.1.44 port 22.


I hope you can find something. I try to get more Infos about Sogo on another forum.

Thanks to all
Greetings
Luca

[lucaegloff]

Hi again

In a Sogo-Group a user told me:
"If you can't login ssh then something has seriously gone wrong with the network stack and the box needs to be rebooted for sure."

Is that right?
I tried to log in from the console and get a "permission Denied". At least it's an answer! from a remote host, I receive no answer.
Hope this helps.

Luca