Hi
I faced a problem while booting linux which is as follows;-
*************************************************
Inode 146180 has illegal block(s)
xauth:error in locking authority file /home/root/.Xauthority
Fatal Server Error:
Could not create lock file in /tmp/tXo-lock
... (1 Reply)
Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday..
Any suggestions what could be... (9 Replies)
We have had a server (Solaris 2.6) hardisk crash. When booting the server we get:
ok> boot -S
Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0
short read 0x2000 chars read
disk read error
The only way we can get into the console is to
ok> boot cdrom
whereby everything (e.g.... (3 Replies)
Is it possible for a group of servers to monitor each other and then send an alert if one of them is no longer 'alive'?
Or if its easier have one server that monitors the other five and then sends an alert.
If so how would this be done?
Thanks (3 Replies)
Is it true that you can't have the crash dump server/client on the same server?
I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump.
if someone is having problem with high... (0 Replies)
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Hi there.
Well i have a really bad problem with my server:
UnixWare Version 5 Release 7
The system crash :wall: and show the error:
Panic: Kernel-mode address fault on user address 0x00000004 :eek:
If anyone knows about the reason of this error please give me a help
Sorry by my english.... (3 Replies)
The steps to test the problem
1. Open TCP Server
2. Open TCP Client
3. TCP Client sends data to Server.
4. Close TCP Server and the client also crash without any notification
Second wonderful test:
1. Comment the following statement in Client.c (at line 168) and compile it
Writen(... (1 Reply)
hi,
i would like to configure netdump, but saving the var/crash in the server itself, not in another server.
could anybody tell me if this is possible?
thanks (4 Replies)
Hi there
I've bought a used System p 9115-505. When I attach the LAN cable to my router the HMC receives an IP address from my router, but the HMC is unreachable. There are no open ports.
Does anybody know that problem?
Any help greatly appreciated. Greetings from Italy! (2 Replies)
Discussion started by: mediaset23
2 Replies
LEARN ABOUT DEBIAN
virtuoso-t
VIRTUOSO-T(1)VIRTUOSO-T(1)NAME
virtuoso-t - OpenLink Virtuoso Opensource Server
SYNOPSIS
virtuoso-t [-fcnCbDARwMKrBd] [+foreground] [+configfile arg] [+no-checkpoint] [+checkpoint-only] [+backup-dump] [+crash-dump] [+configfile
arg] [+restore-crash-dump] [+wait] [+more arg] [+dumpkeys arg] [+restore-backup arg] [+backup-dirs arg] [+debug] [+pwdold arg]
[+pwddba arg] [+pwddav arg]
virtuoso-t [+help]
DESCRIPTION
This manual page documents briefly the virtuoso-t command.
This manual page was written for the Debian distribution because the original program does not have a manual page. Instead, it has docu-
mentation in the 'doc' VAD package.
virtuoso-t is the OpenLink Virtuoso server
OPTIONS
A summary of options is included below. For a complete description, see the 'doc' VAD package.
+foreground
run in the foreground
+configfile
use alternate configuration file
+no-checkpoint
do not checkpoint on startup
+checkpoint-only
exit as soon as checkpoint on startup is complete
+backup-dump
dump database into the transaction log, then exit
+crash-dump
dump inconsistent database into the transaction log, then exit
+crash-dump-data-ini
specify the DB ini to use for reading the data to dump
+restore-crash-dump
restore from a crash-dump
+wait wait for background initialization to complete
+mode specify mode options for server startup (onbalr)
+dumpkeys
specify key id(s) to dump on crash dump (default : all)
+restore-backup
default backup directories
+backup-dirs
run in the foreground
+debug Show additional debugging info
+pwdold
Old DBA password
+pwddba
New DBA password
+pwddav
New DAV password
FILES
/etc/virtuoso/virtuoso.ini
The configuration file to control the behaviour of the main instance of virtuoso-t.
SEE ALSO
The programs are documented fully by the 'doc' VAD package.
17 April 2013 VIRTUOSO-T(1)