Xinet uses the
at_log.old files to monitor how Xinet is being used over the internet and eventually log generic errors, like licensing problems.
at_log information can be viewed under the Logging->Xinet System page in the nativeadmin GUI:
It can also be found in the following folder in the Xinet server:
- Here is an example of a licensing issue shown in the
at_log, when there was actually another old server running with the same serial number.
[Fri Apr 5 14:10:26]No AFP license found - running a 2-user demo [Fri Apr 5 14:10:27]spoolserv: QueueMaster server for "mtr-lx-adv01.xxx.com" version 18.0.2 started [Fri Apr 5 14:10:27]jgui: Xinet GUI Server started on port 5969 [Fri Apr 5 14:10:28]fpod: FPO creation daemon started, allows 10 concurrent fpo generators [Fri Apr 5 14:57:31]ksd AFP server mtr-lx-adv01.xxx.com exiting on signal 2 [Fri Apr 5 14:57:31]ksd(27293): Kerberos Disabled (no cred for "afpserver/mtr-lx-adv01.xxx.com@ZZZ.COM") [Fri Apr 5 14:57:31]ksd(27296): cannot create AppleTalk service: Address family not supported by protocol [Fri Apr 5 14:57:32]ksd(27296): Another host is using serial number 50323 - running in DEMO mode [Fri Apr 5 14:57:32]AFP server "mtr-lx-adv01.xxx.com" started (pid 27296, hint 0), version 18.0.2 [Fri Apr 5 14:57:32]No AFP license found - running a 2-user demo
- Sometimes the issue might be that more than one main ksd process is running on the same server (resulting in the same error messages in the
at_log). To confirm this you need to check ksd processes:
ps -edf | grep ksdIn normal operation it should look like this:
- If there are more odd-looking ksd processes and you have an error like mentioned above you can reboot the server or restart the Xinet service with the following steps:
- Stop the service:
- Check if any ksd process is still running. If so, kill them using the process id (PID) as the parameter for the command:
kill PIDNote: The PID is identified in the same command to list the active process, as in this image:
- Then restart the service with the command: