What do we make of this?

IRIX and IRIX software discussion including open source and commerical offerings.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
uunix
Donor
Donor
Posts: 1796
Joined: Sun Mar 27, 2011 12:48 pm
Location: Stourbridge / England / UK

What do we make of this?

Unread postby uunix » Tue Sep 13, 2016 1:43 pm

So, classic.. nothing changed, booting OK one day, the next this...

Code: Select all

                           Starting up the system...

IRIX Release 6.5 IP35 Version 07202013 System V - 64 Bit
Copyright 1987-2006 Silicon Graphics, Inc.
All Rights Reserved.

Setting rbaud to 19200
NOTICE: /hw/module/001c01/Ibrick/xtalk/14/pci/2/scsi_ctlr/0:  1068 SAS/SATA firmware version 1.18.42.0
Selecting SN11
WARNING: preposterous time in file system
WARNING: CHECK AND RESET THE DATE!
WARNING: preposterous time in file system
WARNING: CHECK AND RESET THE DATE!
NOTICE: Starting failsoftd
The system is coming up.
Mounting filesystems:

Configuring ef0 as Fuel
add net default: gateway 192.168.1.254
Network daemons: portmap.
Name services: nsd.
Internet daemons:UX:suattr: ERROR: Sorry
 inetdUX:suattr: ERROR: Sorry
 timed.
IP Address Configuration:
        Starting DHCP client on Primary interface ef0
No Gateways defined.
No DNS server defined.
No NIS servers defined.
done.
Partition Config daemons : mkpd.
UX:suattr: ERROR: Sorry
UX:suattr: Sorry
Adding swap areas declared in /etc/fstabUX:suattr: ERROR: Sorry
.
Adding virtual swap.
UX:suattr: ERROR: Sorry
Mailer daemons: UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
none.
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
Starting lp spoolerlpcheck: LP Administrator not in password file
.
First RE may not be null
First RE may not be null
First RE may not be null
First RE may not be null
UX:suattr: ERROR: Sorry
Must be logged in as root to execute this
Tape Support Daemon: tsdaemon
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
UX:suattr: ERROR: Sorry
S95availmon: esp chkconfig flag is off. No action.
Removable media daemon: mediadUX:suattr: ERROR: Sorry
.
Resource management daemon: not started

System event collection:UX:suattr: ERROR: Sorry
 rtmond.
UX:suattr: ERROR: Sorry
The system is ready.

INIT: Command is respawning too rapidly.  Check for possible errors.
id:  t1 "/sbin/suattr -C CAP_FOWNER,CAP_DEVICE_MGT,CAP_DAC_WRITE+ip -c "exec /sbin/getty ttyd1 console"         # alt console"


The last message then continues and we get no completed boot up..

So what did change prior.

Well, Set up network (DHCP - but manually added default gateway).
Changed nvram console to d
Connected Serial.
But after I had done that it still booted fine many times, until I think, I removed the power & thus the time was lost.

So booted into single user & set the date..
Rebooted
And Viola.. System is up and running..

I am wondering if suattr is setting some file attributes via su and since the date was preposterous it just couldn't? But this has booted prior many times, with the date incorrect!

Anyway, defiantly need to sort the clock on this FUEL.
-----------------------------------------------------------------------
Hey Ho! Pip & Dandy!
:Octane2: :O2: :Indigo: :Indy:
-----------------------------------------------------------------------

robespierre
Posts: 1555
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: What do we make of this?

Unread postby robespierre » Tue Sep 13, 2016 3:08 pm

suattr is part of the "Trusted IRIX" TCSEC B1 suite for Mandatory Access Control. It partitions the privileges required to perform system actions into ~ a dozen capabilities or compartments: a process running as root does not automatically have access to the entire machine, but only those capabilities that it holds. In order to activate the privileges to access certain devices or features, the script must run suattr, which checks if the capability is allowed and then adds it to the process.

Since the errors were produced by a bad date, it looks like suattr is checking the validity of the request for privileges by verifying the date.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:


Return to “IRIX and Software”

Who is online

Users browsing this forum: No registered users and 1 guest