![]() Snap! FortiGate firewalls, Pixel 7, Neeva, Cat's Eye Nebula, Uranus, & more Spiceworks Originals.:)Or, you know, if you don't have a pet dinosaur, you can post other, lesser dinosaurs, since I suppose it is their month too. October is International Dinosaur Month, so let's see those SpiceRex pics, taken in the wild. Discovered that there was a database update that needed to be applied overni. Our IT Manager is out for vacation, which is not a big deal, but there are often days when staff are needy. Yesterday was a day.In-Office was insane. Overnight Database updates, found myself looking at the business end of a taser! Water Cooler.It seems remoteĬonsole ok prompt can not get via ALOM unless the console serial port In addition, I tried all keystrokes recommended byĮveryone, STOP+A feature still cannot be achieved. Login prompt, I have no way to get the ok prompt since the auto-boot? is The server power from sc>, however, the process always ended up console I did poweroff+poweron or reset for recycle ![]() I have no problem with toggling between sc>Īnd console login prompt. Yes, I use putty to connect from window XP to a jump server, from there Http:/ / sg - Free Solaris Script Compiler This command causes the SC to send a break to the managed system OS which causes Solaris to drop into either kmdb or OBP depending on the mode in which Solaris was booted. Please forgive if already covered but have you tired the 'break' command from the sc> prompt? Then you can do a find on /a to find files added in the last week, files over a certain size (be careful some are important). You can also boot from CDROM and mount the root filesystem to /a, look for instructions under recovering root password.īut you will have to reboot the system and it will be out of use while you fix it (it is broke now anyways) These are often large and deleting several of these might help.Īt this point, find and ls -lr is probably trashed until you find a couple of large files to delete This is a difficult thing, find out if anyone is logged in a root, and then try and get some tools going. I say put logs and home and /usr/local under thier own fs, as well as common user FS. This is why I oppose the popular opionion in putting everything under the / filesystem. If you can get a login, otherwise you may need to just power downĪnd hope you dont have a live database on this server. ![]() Subject: RE: Cannot console login due to filesystem full > qualities when being hired into a new job. :) shows your versatility and persistence. > I did a Google search for "solaris stop-a" and found several pages addressing > checks, with 'yes' answered to every question. In that case you should execute an 'fsck -y' to perform file system > Since '/var' is already full, it may not be 'clean' when you boot up via the > You should be able to execute a 'mount -a' to mount all the local partitions. once you get in, su to root then you can remove > You can log in as any other user beside root. So is better to reboot system, start from CD, Logs, so in normal system the situation is the same for all users i.e. and write the group back with your success and any special thingsĪctually is not sure you can login as ordinary user because of system The utmpx entry occurs cause there is no additional space to add a record of yourĪttempt to the 'utmpx' file somewhere under /var. Get thisįixed, return the system to normal usage, then focus on cleaning up log size To tape (via tar) or to another device and compress them along the way. I'd suggest moving some of the older rotated log files out, Recommend futzing with anything else, and don't FIX any other problems either. ![]() If your '/var' filesystem is full, then you'll need to free some space in /var. I'm not sure of the 'alternate'Ĭombination that will equate to Stop-A, at least there is one for the serial ![]() Well, you can get in via an alternate means. ![]()
0 Comments
Leave a Reply. |