omniNames fails to start on boot

Bug #1797777 reported by David Terrett on 2018-10-14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
omniorb-dfsg (Ubuntu)

Bug Description

/etc/init.d/omniorb4-nameserver thinks that the omniNames log file has the extension .log but as of omniorb 4.2 it is .dat. If the log file doesn't exist, the script creates it. omniNames then refuses to start because both .dat and .log files exist.

The fix is to change the log file extension to .dat.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: omniorb 4.2.2-0.8
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 14 15:22:53 2018
InstallationDate: Installed on 2018-07-13 (93 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
 PATH=(custom, no user)
SourcePackage: omniorb-dfsg
UpgradeStatus: No upgrade log present (probably fresh install)

David Terrett (david.terrett) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in omniorb-dfsg (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers