  | 
			
				SoftTree Technologies 
				Technical Support Forums
			 | 
		 
		  | 
	 
	 
	
	
	
		
	
	
	
		| Author | 
		Message | 
	 
	
		
			seanc217 
			 
			
  
			
			
				Joined: 23 May 2007 Posts: 272
  | 
			 
			  
		 | 
		
			
				  Unmarshal errors | 
				     | 
			 
			
				I'm seeing alot of errors that get returned to me and the job never got kicked off.
 
Is this some type of network or communication error??
 
 
See below...
 
 
 is:   java.io.EOFException
 
27-May-2012 09:51:18 AM 3       7xScmRht5hhVbDPyGb3xspoWOaY=    362     01_check_st_ctrl        Remote job failed. Error unmarshaling return; nested exception is:   java.io.EOFException
 
27-May-2012 09:51:19 AM 3       7xScmRht5hhVbDPyGb3xspoWOaY=    1061    010_check_fidnnm86      Remote job failed. Error unmarshaling return; nested exception is:   java.io.EOFException
 
27-May-2012 09:51:20 AM 3       7xScmRht5hhVbDPyGb3xspoWOaY=    1420    010_check_ach_s1_report_04_trigger      Remote job failed. Error unmarshaling return; nested exception is:   java.io.EOFException
 
27-May-2012 09:51:21 AM 3       7xScmRht5hhVbDPyGb3xspoWOaY=    2551    030_run_s1_sales_pcr7_wave2_init        Remote job failed. Error unmarshaling return; nested exception is:   java.io.EOFException
 
27-May-2012 09:51:21 AM 1       7xScmRht5hhVbDPyGb3xspoWOaY=    2551    030_run_s1_sales_pcr7_wave2_init        Job has been disabled!
 
27-May-2012 09:51:21 AM 2       7xScmRht5hhVbDPyGb3xspoWOaY=    2551    030_run_s1_sales_pcr7_wave2_init        Error message sent.
  | 
			 
		  | 
	 
	
		| Sun May 27, 2012 10:27 am | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				It sounds like the job is dying on the remote agent side before it can return its status to the scheduler, thus EOFException (end-of-file on communication channel). I think I've seen such errors before. Which version of the scheduler are you running? Is the agent version the same?
  | 
			 
		  | 
	 
	
		| Sun May 27, 2012 10:57 am | 
		          | 
	 
	
		  | 
	 
	
		
			seanc217 
			 
			
  
			
			
				Joined: 23 May 2007 Posts: 272
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				I think I may know part of the issue.
 
The log file on the agent was 6.4 GB.
 
 
Also I think there may have been some issues with the agent process itself.
 
So, I restarted the agent, which creates a new log file.
 
 
We will see how it goes, feel free to comment on the error and if you think that may have been part of the issue.
 
 
Thanks.
  | 
			 
		  | 
	 
	
		| Sun May 27, 2012 10:58 am | 
		          | 
	 
	
		  | 
	 
	
		
			seanc217 
			 
			
  
			
			
				Joined: 23 May 2007 Posts: 272
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Hi, since I have restarted the agent and cleaned up the log files all seems well so far.
 
All agents and master scheduler are on the same version which is 4.4.322 Multi-Platform.
  | 
			 
		  | 
	 
	
		| Sun May 27, 2012 2:34 pm | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				I suggest scheduling a weekly or monthly job to archive (zip with a time suffix) and delete agent log file. Typically this is done using mv command to move active log file to log archive directory  then gzip to compress it and rename with a time suffix and lastly using rm command to the delete log file from archive directory and leave gzipped  copy only.
  | 
			 
		  | 
	 
	
		| Sun May 27, 2012 9:26 pm | 
		          | 
	 
	
		  | 
	 
	
		 | 
	 
 
  
	 
	    
	   | 
	
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
  | 
   
 
		 | 
	 
	  |