04-27-2008
example
=======
Server A
192.168.10.10 ABOX loghost
192.168.10.20 BBOX
Server B
192.168.10.20 BBOX
192.168.10.10 ABOX loghost
Server A check your /etc/hosts to see if you host ip address has a loghost next to it.
Server B check the /etc/hosts to see if there is an entry that pointing to Server A as the loghost
check your /etc/syslog.conf
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hiho,
my sun ultra1 print me in my /var/adm/message file:
Aug 3 03:16:29 dazinger1 raid: AEN event =
Host=3Ddazinger1 Ctrl=3D1T04359235 Dev=3Dc1t1d0
Aug 3 03:16:29 dazinger1 raid: ASC=3DA0 =
ASCQ=3D00 FRU=3D00 LUN=3D00 LUN Stat=3D00
Aug 3 03:16:29 dazinger1 raid: =... (3 Replies)
Discussion started by: pressy
3 Replies
2. UNIX for Advanced & Expert Users
Hello group,
How can I separate "named daemon" messages to the other file instead of /var/adm/messages. I still want all other daemons log the messages to /var/adm/messages.
i.e.
named => /var/adm/named.message
other daemons => /var/adm/messages.
I searched unix.com, and google but I still... (5 Replies)
Discussion started by: dannytrinh
5 Replies
3. Solaris
hi sirs
can u tell the difference between /var/log/syslogs and /var/adm/messages
in my working place i am having two servers.
in one servers messages file is empty and syslog file is going on increasing..
and in another servers message file is going on increasing but syslog file is... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
4. UNIX for Advanced & Expert Users
The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux.
I checked the log level in Linux and they seem OK.
Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Discussion started by: gomes1333
2 Replies
5. Solaris
Hi,
Is the contents in /var/log/syslog and /var/adm/messages are same??
Regards (3 Replies)
Discussion started by: vks47
3 Replies
6. Solaris
Hi Friends,
Please help me to resove this issue ASAP.
Nov 17 16:25:52 server1 sendmail: pAH8Pnh22099: SYSERR: putoutmsg (NO-HOST): error on output channel sending "553 5.1.3 @123.com.... User address required": File too large
Nov 17 16:25:53 server1 sendmail: pAH8Pnh22099:... (1 Reply)
Discussion started by: holds_me
1 Replies
7. Solaris
Hi,
I am getting the below messsage in /var/adm/message after patching but sendmail is working after restoring the backup file.
sendmail: q4G7U1Cj014774: SYSERR(root): 127.0.0.1 config error: mail loops back to me (MX problem?)
sendmail: q4G801cw025824: SYSERR(root): 127.0.0.1 config... (3 Replies)
Discussion started by: fayaz
3 Replies
8. Solaris
Good Morning..
Hello Everyone, I've been receiving this message in /Var/adm 2 days ago, I'm a new administrator for Solaris 10 and don't know what it means..
Thanks for your help
Here is the full message:
Feb 18 03:30:45 sun3000 ebus: se0 at ebus0: offset 1,400000
Feb 18 03:30:45... (4 Replies)
Discussion started by: alexelchivo
4 Replies
9. Solaris
Hi All
I am facing an issue with our new solaris machine.
in /var/adm/messages
root@Prod-App1:/var/tmp#
root@Prod-App1:/var/tmp#
root@Prod-App1:/var/tmp# cat /var/adm//messages
Apr 20 03:10:01 Prod-App1 syslogd: line 25: WARNING: loghost could not be resolved
Apr 20 08:24:18 Prod-App1... (0 Replies)
Discussion started by: javeedkaleem
0 Replies
10. Solaris
Hi All
I am facing an issue with our new solaris machine.
in /var/adm/messages
Apr 22 16:43:05 Prod-App1 in.routed: interface net0 to 172.16.101.1 turned off
Apr 22 16:43:33 Prod-App1 mac: NOTICE: nxge0 link up, 1000 Mbps, full duplex
Apr 22 16:43:34 Prod-App1 mac: NOTICE: nxge0 link... (2 Replies)
Discussion started by: javeedkaleem
2 Replies
LEARN ABOUT DEBIAN
rlm_ippool_tool
RLM_IPPOOL_TOOL(8) System Manager's Manual RLM_IPPOOL_TOOL(8)
NAME
rlm_ippool_tool - dump the contents of the FreeRadius ippool database files
SYNOPSIS
If an ipaddress is specified then that address is used to limit the actions or output.
rlm_ippool_tool [-a] [-c] [-o] [-v] session-db index-db [ipaddress]
Mark the entry nasIP/nasPort as having ipaddress
rlm_ippool_tool -n session-db index-db ipaddress nasIP nasPort
Update old format database to new.
rlm_ippool_tool -u session-db new-session-db
DESCRIPTION
rlm_ippool_tool dumps the contents of the FreeRADIUS ippool databases for analyses or for removal of active (stuck?) entries.
Or with the -n argument adds a usage entry to the FreeRADIUS ippool databases.
OPTIONS
-a Print all active entries.
-c Report number of active entries.
-r Remove active entries.
-v Verbose report of all entries.
-o Assume old database format (nas/port pair, not md5 output).
-n Mark the entry nasIP/nasPort as having ipaddress.
-u Update old format database to new.
EXAMPLES
Given the syntax in the FreeRadius radiusd.conf:
ippool myippool {
range-start = 192.168.1.0
range-stop = 192.168.1.255
[...]
session-db = ${raddbdir}/ip-pool.db
ip-index = ${raddbdir}/ip-index.db
}
To see the number of active entries in this pool, use:
$ rlm_ippool_tool -c ip-pool.db ip-index.db
13
To see all active entries in this pool, use:
$ rlm_ippool_tool -a ip-pool.db ip-index.db
192.168.1.5
192.168.1.82
192.168.1.244
192.168.1.57
192.168.1.120
192.168.1.27
[...]
To see all information about the active entries in the use, use:
$ rlm_ippool_tool -av ip-pool.db ip-index.db
NAS:172.16.1.1 port:0x2e8 - ipaddr:192.168.1.5 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x17c - ipaddr:192.168.1.82 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x106 - ipaddr:192.168.1.244 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x157 - ipaddr:192.168.1.57 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x2d8 - ipaddr:192.168.1.120 active:1 cli:0 num:1
NAS:172.16.1.1 port:0x162 - ipaddr:192.168.1.27 active:1 cli:0 num:1
[...]
To see only information of one entry, use:
$ rlm_ippool_tool -v ip-pool.db ip-index.db 192.168.1.1
NAS:172.16.1.1 port:0x90 - ipaddr:192.168.1.1 active:0 cli:0 num:0
To add an IP address usage entry, use:
$ rlm_ippool_tool -n ip-pool.db ip-index.db 192.168.1.1 172.16.1.1 0x90
rlm_ippool_tool: Allocating ip to nas/port: 172.16.1.1/144
rlm_ippool_tool: num: 1
rlm_ippool_tool: Allocated ip 192.168.1.1 to client on nas 172.16.1.1,port 144
SEE ALSO
radiusd(8)
AUTHORS
Currently part of the FreeRADIUS Project (http://www.freeradius.org) Originally by Edwin Groothuis, edwin@mavetju.org
(http://www.mavetju.org)
Mailing list details are at http://www.freeradius.org/
RLM_IPPOOL_TOOL(8)