Re: [Help-gnu-radius] Not writing wtmp?

[Sergey Poznyakoff]

> Notice: NOT writing wtmp record (1) for `tink',NAS kit-max1,port 490

The error message immediately preceding this should clarify the
reason. Most probably you will find one of these:

1) logout: entry for NAS %s port %d has wrong ID (expected %s found %s)

Somehow the start accounting record of the next session for this
NAS/port combination has been processed before the stop accounting
record reached the server. Usually this means the original start
record was lost, and the NAS retransmitted it later, but by the
time the record was received, the entry was already marked as
being used by another session. 

2) login: entry for NAS %s port %d duplicate

The login packet has already been processed and replied. Possibly the
reply was not received by the NAS (either network error of NAS load
was too high).

3) login: entry for NAS %s port %d wrong order

Trying to write a start entry radiusd discovered that this NAS/port
combination is already marked with stop for the same session id.
This means that the stop record reached radius server before the
start record (possibly due to network issues or high server load).
Usually the corresponding session has zero Acct-Session-Time
attribute.

4) logout: login entry for NAS %s port %d not found

Trying to write a stop entry the server did not found a corresponding
start entry. Possibly the start entry was lost (again, either network
problems or high server load).


Regards,
Sergey