Imagen de Sergio Balaguer Llum error al conectar al servidor n4d (XMLRPC)

Imagen de Sergio Balaguer Llum error al conectar al servidor n4d (XMLRPC)

by Deleted user -
Number of replies: 4
Hola, no se como solucionar este problema, me sale este error cuando entro en Llum. "Hubo un error intentando conectar al servidor n4d (XMLRPC)"

Cuando instalo el servidor por primera vez si que puedo entrar y añadir usuarios pero después, no se si después de actualizar, ya no puedo añadir usuarios porque tengo este error.

He formateado el ordenador por si había instalado alguna cosa que hubiera afectado pero la segunda vez que he probado me ha pasado lo mismo.

¿Cómo puedo solucionar esto? ahora no puedo importar el archivo del Gescen y dar de alta a los usuarios.

He lanzado el asistente ZERO SERVER WIZAR como servidor independiente varias veces por si era eso y he usado el actualizador de sistema "Actualizador de Lliurex".

Si ejecuto desde el terminal sale esto:

o@server:~$ sudo llum
INFO: You may use a custom server ip as a parameter to connect to a n4d-server. Ex.: llum 172.25.25.54
https://server:9779
System.Net.WebException: Error: ConnectFailure (Connection refused) ---> System.Net.Sockets.SocketException: Connection refused
at System.Net.Sockets.Socket.Connect (System.Net.EndPoint remote_end) [0x00000]
at System.Net.WebConnection.Connect (System.Net.HttpWebRequest request) [0x00000]
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetRequestStream (IAsyncResult asyncResult) [0x00000]
at System.Net.HttpWebRequest.GetRequestStream () [0x00000]
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke (System.Object clientObj, System.Reflection.MethodInfo mi, System.Object[] parameters) [0x00000]
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke (System.Reflection.MethodInfo mi, System.Object[] Parameters) [0x00000]
at XmlRpcProxy85707d48-ca17-4631-a266-dfe5efe0c72b.login (System.String[] user_info, System.String class_name, System.String[] user_pass) [0x00000]
at llum.LoginWidget.OnConnectButtonClicked (System.Object sender, System.EventArgs e) [0x00000]
In reply to Deleted user

Re: Imagen de Sergio Balaguer Llum error al conectar al servidor n4d (XMLRPC)

by Deleted user -
Hola Sergio:

Pots postejar el contingut del fitxer /etc/pam.d/common-auth que tens al servidor???
In reply to Deleted user

Re: Imagen de Sergio Balaguer Llum error al conectar al servidor n4d (XMLRPC)

by Deleted user -

Hola a mi em passa lo mateix i per ara no hem sabut com solucionar-lo.

Aquest és el contingut del fitxer common-auth
#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules. See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
auth [success=3 default=ignore] pam_krb5.so minimum_uid=1000
auth [success=2 default=ignore] pam_unix.so nullok_secure try_first_pass
auth [success=1 default=ignore] pam_winbind.so krb5_auth krb5_ccache_type=FILE cached_login try_first_pass
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth optional pam_smbpass.so migrate
# end of pam-auth-update config

 A vore si em podeu a ajudar. Gracies

In reply to Deleted user

Re: Imagen de Sergio Balaguer Llum error al conectar al servidor n4d (XMLRPC)

by Deleted user -

El sistema està actualitzat? Acabem de traure alguna revisiò que arregla un parell de cosses. , una volta ja està actualitzat :

Pots ejecutar en consola

status n4d

Açò ha de tornar "running".  si no ho fà , fes:

sudo n4d-server 

açò hauria de ficar el dimoni en marxa. Si no ho fà. ... esperem noticies.

In reply to Deleted user

Re: Imagen de Sergio Balaguer Llum error al conectar al servidor n4d (XMLRPC)

by Deleted user -

Hola Sergio,

El sistema està actualitzat.

He executat status n4d i em torna n4d stop/waiting.

Al executar sudo n4d-server em torna el següent error

Traceback (most recent call last):
  File "/usr/sbin/n4d-server", line 248, in <module>
    obj=imp.load_source("core","/usr/share/n4d/xmlrpc-server/core.py")
  File "/usr/share/n4d/xmlrpc-server/core.py", line 74, in <module>
    s=globals()[plugin.class_name]()
  File "/usr/share/n4d/python-plugins/Golem.py", line 25, in __init__
    self.pw=obj4.PasswordManager()
  File "/usr/share/n4d/python-plugins/PasswordManager.py", line 16, in __init__
    os.mkdir(PasswordManager.LOG_PATH)
OSError: [Errno 2] No existe el fichero o el directorio: '/net/var/lib/n4d'