Truxton Service

The Truxton Service is a Windows Service that hosts the exploitation process scheduling as well as the message bus traffic concentrator.

Overview

Each Truxton machine that participates in the exploitation of data needs something that determines what should be running and when. The primary job of the Truxton service is to keep the processes described in TruxtonService.xml going. Should a process exit while processing a file, Truxton Service will notice that and start a new instance.

Tuning

The service will monitor the TruxtonService.xml settings file for changes and implement those changes without need to restart the service. They will take immediate affect. If you change the number of instances of an ETL process, the change will take place when you save the file. Manipulating this file allows you to add or remove exploitation processes as needed.

Scheduling

As shipped, all ETL processes will run 24x7. You can alter the configuration file and make your own work schedule. One example would be to have the processes run Monday-Friday 6pm until 6am and all day on Saturday and Sunday.

Controlling

The Truxton Service will appear as "Truxton" in the Windows Services Control Panel app and can be controlled from there. To start Truxton, execute this in a command window:

net start truxton

To stop Truxton:

net stop truxton

To disable Truxton:

sc config truxton start=disabled

To re-enable Truxton:

sc config truxton start=auto

Event Log Messages

The Truxton Service will log events to the Application log.

Number	Type	Event Log Message	Meaning
1	Informational	Truxton Service successfully installed by %1.	Records who installed the service
2	Informational	Truxton Service successfully removed by %1.	Records who removed the service
4	Informational	Service started.	Logs when the service is started
5	Informational	Service stopped.	Logs when the service is stopped
12	Informational	Going off duty (%1)	The service is going to off scheduled duty. The numeric value is for internal debugging.
15	Informational	Starting %1 from thread %2	Records the ETL command line and from what thread in the service it is being spawned.
16	Informational	Desired number of %4 instances is %1 while %2 are running, will start %3 instances from thread %5	Records how many new instances of the ETL process will be started
17	Informational	Desired number of %4 instances is %1 while %2 are running, will stop %3 instances from thread %5	Records how many instances of an ETL process will be stopped because there are too many
18	Informational	Stopping %1 process id %2 from thread %3	Stopping an individual process
19	Informational	Not stopping %1 process id %2 because it is exempt from thread %3.	Some ETL processes cannot be stopped because they have been marked as exempt from control
20	Informational	Told %1 process id %2 to exit gracefully from thread %3.	A monitored process has been signaled to terminate in an orderly manner
21	Informational	Could not get exit handle for %1 process id %2 to tell it to exit gracefully. %3	A monitored process did not register an exit-gracefully handle
22	Informational	%1 process id %2 has no control block and is not a batch file.	A monitored process is not a batch file and not created using the Truxton SDK
23	Informational	Batch command to stop ETL: %1	A batch file based ETL needs to stop. The batch file registered as the "stop" command is now being executed
28	Error	Can't open %1 process id %2 from thread %3 error code %4 : %5	The service cannot open the process to monitor. Normally this happens when the service tries to open an ETL process that was run by a user from the command line.
29	Error	Can't open shared memory block for %1 process id %2 error code %3 - %4	The service got a handle to the process but cannot open the shared memory block of the ETL process.
30	Error	Can't get pointer to shared memory block for %1 process id %2	A pointer to the shared memory block could not be retrieved
31	Error	Invalid signature on shared memory for %1 process id %2	The shared memory contains an invalid control structure
32	Informational	Truxton service has been told to stop. Stopping ETLs now.	The service control manager is stopping the service.
33	Informational	ETLs were stopped.	The service finished telling all of the managed ETL processes to stop.
34	Informational	Finished processing stop message.	The service finished handling the stop message from the service control manager.
35	Informational	Truxton service has been told to shut down. Stopping ETLs now.	The service control manager is telling us the machine is shutting down.
36	Informational	ETLs were shut down.	The service finished stopping the ETLs
37	Informational	Finished processing the shut down message.	The service finished handling the shut down message from the service control manager.
38	Informational	ETL process %1 process id %2 is under control of %3 and not us (%4).	The ETL process is being controlled by a process that is not the Truxton Service.
39	Informational	Going off duty because the license is bad.	The software license is garbage. Not valid is any way shape or form. It has been folded, spindled or mutilated.
40	Informational	This machine has been decommissioned and will no longer run Truxton.	Truxton was removed from this system and told to never run here again.
41	Informational	Updating solr.cmd failed, could not copy from "%1" to "%2" error code %3 - %4	An old solr.cmd batch file was found but could not be upgraded.
42	Informational	The Truxton Service is acting as a connection concentrator for the message bus. All local ETLs will use this process to communicate to the Message Bus Server.	Message concentrator is running.
43	Informational	Could not load Message Bus Provider "%1" error code %2 - %3	The DLL that implements the message bus could not be loaded.
44	Informational	Successfully loaded and now using Message Bus Provider "%1"	Records the DLL that is being used to provide message bus services
45	Informational	"justconnie" was specified, starting the message bus concentrator	The user specified on the command line that the process should only act as a message concentrator and not an ETL process shephard
46	Informational	"justconnie" was specified, finished	The user specified on the command line that the process should only act as a message concentrator and it finished
47	Informational	"mqconcentrator" was set to true, Truxton Service will now act as a concentrator (or connection pooler) for ETL message bus traffic on this machine.	mqconcentrator was set to true, message concentration is in effect
48	Informational	"mqconcentrator" was set to false, Truxton Service will run normally.	Truxton service is acting only as an ETL process shephard
49	Informational	Connection concentrator settings file is "%1"	Tells you which settings file is being used
50	Informational	%1	The setting being used
51	Informational	syslog is active at address %1 port %2	Records where syslog messages are being sent
52	Informational	syslog is not being used	Lets you know that syslog is not in use
53	Informational	Loading the Message Bus Provider in %1	Tells you the name of the file providing Message Bus services
54	Informational	Concentrator: %1	Used when the message bus provider is logging an informational message
55	Warning	Concentrator Warning: %1	Used when the message bus provider is logging a warning message
56	Error	Concentrator Error: %1	Used when the message bus provider is logging an error message
57	Informational	Opening the Message Concentrator Provider	The message bus provider was loaded, now the "open" method will be called
58	Informational	Successfully opened the Message Concentrator Provider	The "open" call succeeded
59	Error	Failed to open the Message Concentrator Provider	The "open" call failed
60	Informational	Message Concentrator beginning to wait for incoming connections	The concentrator is ready to accept incoming connections
61	Informational	Setting the socket to reuse address	Setting a socket option
62	Informational	Connie got a new connection	The message concentrator added a new connection
63	Informational	New thread to handle connection from %1 (%2)	The message concentrator has spawned a thread
64	Informational	Message concentrator socket error %1	The message concentrator encountered a socket error
65	Informational	Cannot read all of the data from the socket, exiting message concentrator thread	The message concentrator could not read from a socket
66	Informational	Syslogging is already on	Syslogging was already on when told to turn it on
67	Error	Could not parse the SOLR Stop Arguments to determine SOLR port number. Arguments were "%1"	The parameters for SOLR could not be parsed
68	Error	Could not parse the SOLR port number from "%1" (argument %2 of %3 from "%4")	The parameters for SOLR could not be parsed
69	Error	SOLR is not running because we could not get the SOLR page. Read %1 bytes from %2	SOLR doesn't seem to be responding
70	Informational	Starting batch file %1	A batch file is being started
71	Informational	Starting process %1	A process is being started
72	Error	Could not start process %1	A process could not be started
73	Error	Could not find the batch file associated with the $TruxtonData$ variable. "%1" was the substitution value which resulted in a batch file name of "%2" which was not found. The error code was %3 meaning %4	A batch file couldn't be found
74	Error	Could not find the batch file associated with the $TextIndexerData$ variable. "%1" was the substitution value which resulted in a batch file name of "%2" which was not found. The error code was %3 meaning %4	A batch file couldn't be found
75	Error	Could not find the batch file associated with the $TruxtonData$ variable. "%1" was the substitution value which resulted in a batch file name of "%2" which was not found. There was no error, the file just doesn't exist.	A batch file couldn't be found but there was no error reported by the operating system
76	Error	Could not find the batch file associated with the $TextIndexerData$ variable. "%1" was the substitution value which resulted in a batch file name of "%2" which was not found. There was no error, the file just doesn't exist.	A batch file couldn't be found but there was no error reported by the operating system
77	Warning	The %1 executable file is missing.	Truxton must start an instance of an ETL process but the executable file cannot be found. This will be followed by at least one error message 72.