Greetings,

 

I have a fresh install of FRED 2.35.0 on Ubuntu Server 16.04 LTS but the services can’t seem to start, only fred-pyfred is active.

 

The ExecStart commands like: /usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf exit with failure of Error: CORBA NameService not running.

                                                      /usr/sbin/fred-adifd -ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-adifd.conf exit with failure of Error: CORBA NameService not running.

                                                           /usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-pifd.conf exit with failure of Error: CORBA NameService not running.

                                                           /usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-logd.conf exit with failure of Error: CORBA NameService not running.

                                                           /usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-msgd.conf exit with failure of Error: CORBA NameService not running.

                                                           /usr/sbin/fred-rsifd -ORBendPoint giop:tcp::2234 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rsifd.conf exit with failure of Error: CORBA NameService not running.

 

The fred-webadmin log when running /usr/bin/fred-webadmin is as follows:

 

omniORB: (0) 2019-01-16 08:03:11.886060: ERROR! omniORBpy version 4.2 expects stubs version 4.2. Stubs in /usr/lib/python2.7/dist-packages/CosNaming_idl.pyc are version 3.0 (rev 0).

Traceback (most recent call last):

  File "/usr/bin/fred-webadmin", line 8, in <module>

    from fred_webadmin.controller import adif

  File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py", line 38, in <module>

    import fred_webadmin.auth.corba_auth as auth

  File "/usr/lib/python2.7/dist-packages/fred_webadmin/auth/corba_auth.py", line 1, in <module>

    import fred_webadmin.corbarecoder as recoder

  File "/usr/lib/python2.7/dist-packages/fred_webadmin/corbarecoder.py", line 5, in <module>

    from pyfco.recoder import decode_iso_date, decode_iso_datetime, encode_iso_date, encode_iso_datetime

  File "/usr/lib/python2.7/dist-packages/pyfco/__init__.py", line 3, in <module>

    from .name_service import CorbaNameServiceClient

  File "/usr/lib/python2.7/dist-packages/pyfco/name_service.py", line 6, in <module>

    import CosNaming

  File "/usr/lib/python2.7/dist-packages/CosNaming/__init__.py", line 9, in <module>

    import CosNaming_idl

  File "/usr/lib/python2.7/dist-packages/CosNaming_idl.py", line 7, in <module>

    _omnipy.checkVersion(3,0, __file__)

ImportError: Stubs not compatible with omniORBpy version 4.2.

 

Is there a way I can solve this compatibility issure?

 

The process omniorb4-nameserver status output is as follows:

 

omniorb4-nameserver.service - LSB: Start the omniNames Interoperable Naming Service

   Loaded: loaded (/etc/init.d/omniorb4-nameserver; bad; vendor preset: enabled)

   Active: active (exited) since Wed 2019-01-16 07:39:02 SAST; 11min ago

     Docs: man:systemd-sysv-generator(8)

  Process: 28050 ExecStop=/etc/init.d/omniorb4-nameserver stop (code=exited, status=0/SUCCESS)

  Process: 28133 ExecStart=/etc/init.d/omniorb4-nameserver start (code=exited, status=0/SUCCESS)

    Tasks: 0

   Memory: 0B

      CPU: 0

 

Jan 16 07:39:02 fred-test systemd[1]: Starting LSB: Start the omniNames Interoperable Naming Service...

Jan 16 07:39:02 fred-test omniorb4-nameserver[28133]:  * Starting omniORB name server omniNames

Jan 16 07:39:02 fred-test omniorb4-nameserver[28133]:    ...done.

Jan 16 07:39:02 fred-test systemd[1]: Started LSB: Start the omniNames Interoperable Naming Service.

 

 

In fred-eppd.log I found [sessionID 216968] Could not obtain object reference for alias 'EPP_alias'. Check mod_corba's configuration, whoever the module does seem to be enables under apache mods-enabled.

 

What could be the problem?

 

Regards,

Moeketsi Maphoi