SWINST-F-DIRCONSERR

[Solandsystel]

Hello huys,
So I had the partition 6 full at 100 per cent on an oxe R9.
Made some searches here.
I deleted the content of directory /var/tmp

When I launch swinst

An error message is displayed briefly :

SWINST-F-DIRCONSERR, Inconsistent in swinst account
Directory /tmpd/soft_install is missing
Remove the package and re-install it

And after that the swinst menu is displayed as usual.

I recreated the directory with md soft_install
But the error still shows

P.S
I just discovered that some extra errors are displayed when trying to backup mao and OPS on cpu disk.
It seems that I messed up with the wrong directory

Hope that there is a solution without replacing the HD

Thanks to you all for your help

[alex]

I deleted the content of directory /var/tmp

Well , it escalated quickly.

Remove the package and re-install it

Depends on which SW version you have. If its more or less new then run to find location of your swinst rpm package.

Code: Select all

su
find / -name sw*.rpm -print

Search the web for "man rpm" how to install or repair rpm package.

If you have installation media - create VM in Oracle VirtualBox, run OXE installation, restore DB and just ftp the whole /var/tmp directory.

[Solandsystel]

I deleted the content of directory /var/tmp

Well , it escalated quickly.

Remove the package and re-install it

Depends on which SW version you have. If its more or less new then run to find location of your swinst rpm package.

Code: Select all

su
find / -name sw*.rpm -print

Search the web for "man rpm" how to install or repair rpm package.

If you have installation media - create VM in Oracle VirtualBox, run OXE installation, restore DB and just ftp the whole /var/tmp directory.

Hi Alex,

Thanks so much for your precious answer.

The release is R9.0-h1.301-27 on a Cpu7-2, (crystal hardware)

If by installation media, you mean . iso file then the answer is no I don't have it and alcatel has restricted the access to download iso files on the BP site

And if by chance, i grab the iso file somewhere, it would be the first time that i run oxe installation on oracle VM (but i did some windows /linux installation on a VM by the past).

[alex]

The release is R9.0-h1.301-27 on a Cpu7-2, (crystal hardware)

I check with running R9.0-h1.301-50-c system - this is what is in /var/tmp

Code: Select all

(1)xa000000> ll /var/tmp
total 0
-rwxr-xr-x    1 root     root            0 Aug 19 16:01 aging_passwd.txt
prw-r--r--    1 root     root            0 Jul 25 11:34 incid

No tmpd/soft_install directory is there.
Looks like you deleted something else, may be /tmpd directory which in fact is /usr4/tmp

Code: Select all

root@xa000000 mtcl]# find / -name soft_* -print
/usr2/soft_install
/usr3/soft_install
/usr4/tmp/soft_install

[frank]

You most likely deleted /tmpd , which has the soft_install folder in it.
Best would be to do a partition duplication (from other partition to this partition), or better if you have another CPU running the same version, that you did not touch, copy back the tmpd folder with right owners and right rights

[Solandsystel]

The release is R9.0-h1.301-27 on a Cpu7-2, (crystal hardware)

I check with running R9.0-h1.301-50-c system - this is what is in /var/tmp

Code: Select all

(1)xa000000> ll /var/tmp
total 0
-rwxr-xr-x    1 root     root            0 Aug 19 16:01 aging_passwd.txt
prw-r--r--    1 root     root            0 Jul 25 11:34 incid

No tmpd/soft_install directory is there.
Looks like you deleted something else, may be /tmpd directory which in fact is /usr4/tmp

Code: Select all

root@xa000000 mtcl]# find / -name soft_* -print
/usr2/soft_install
/usr3/soft_install
/usr4/tmp/soft_install

Yes! you're right. It is /tmpd not /var/tmp

[Solandsystel]

You most likely deleted /tmpd , which has the soft_install folder in it.
Best would be to do a partition duplication (from other partition to this partition), or better if you have another CPU running the same version, that you did not touch, copy back the tmpd folder with right owners and right rights

Ok Frank that's clear.
Next time I will check if by any chance the unactive partition is duplicated because not all systems have their partitions duplicated.