Docker Otter 3.0.12 with InedoAgent The agent does not have a valid execution temp path

shiv03_9800

On execute "PowerShellDemo" on "InedoAgent", error:
"The agent does not have a valid execution temp path.
Execution run failed."

Tried: on 3 machines: W10/2016/2019 (2019 - in one [Proxmox] host with docker).

With:
new DB Otter (or old from otter-3.0.10)
docker otter:3.0.12
Inedo Agent (v49, a1.b1.c1.d1:80/46336)
Encryption: None or AES
status="Ready" (empty LogMessages)

After execute:

LogMessages: empty
LogFile:
dt: Connection request from a2.b2.c2.d2:nnnnn
dt: Connection established with a2.b2.c2.d2:nnnnn
dt DEBUG [s-x1] start message loop
dt DEBUG [s-x1] waiting for message ...
dt DEBUG [s-x1] message recieved (25 bytes)
dt DEBUG [s-x1] waiting for message ...
dt DEBUG [s-x1] message recieved (17 bytes)
dt DEBUG [s-x1] waiting for message ...
dt: a2.b2.c2.d2:nnnnn disconnected.
dt DEBUG [s-x1] message recieved ((null) bytes)
dt DEBUG [s-x1] terminated message loop
There are folders:
1. %TEMP%:
  C:\Windows\Temp\Inedo
  ExtensionCache\ - with subfolders
  C:\Windows\Temp\InedoAgent\Otter\a2.b2.c2.d2
  Agents
  Extensions
  Temp\ - empty
2. C:\ProgramData:
  C:\ProgramData\Inedo
  SharedConfig\ - with conf
  C:\ProgramData\InedoAgent\ - empty.
cacls on these folders:
- with SYSTEM:F (InedoAgentService runas SYSTEM).
- I added Everyone:F - without changes.

Dan_Woolf

Hi @shiv03_9800,

What account do you have your Inedo Agent running as on your client server? We have seen some issues in the the past with the default temp directory (C:\Windows\Temp\InedoAgent\Otter) when running with the built-in accounts. This doesn't happen often, but we have seen it on a few occasions.

Could you please try adding an <OtterRootPath>Path to your custom temp directory</OtterRootPath> element to your Inedo Agent config? You can do this by:

Create a new temp directory on that server with full permissions to the account that the Inedo Agent service is running as
Edit the InedoAgent.config file under C:\ProgramData\Inedo\SharedConfig
Add the OtterRootPath element directly under InedoAgentConfig root element
Restart the Inedo Agent service

Can you please give this a try?

Thanks,
Dan

shiv03_9800

Hi @Dan_Woolf,

Answer:
1. was as defaullt: BUILTIN\SYSTEM;
2. no changes (the service is started as a new local user, folders appeared in the specified folder [C:\Tmp\otter], the error, subfolders and log is the same).
You retold:
https://docs.inedo.com/docs/inedoagent-configuration-troubleshooting
But in both cases, it is missed workaround that here need to reconfigure in Otter the 'serverX' (pull the settings), for push content to blank temporary directory.
Otherwise - 'droped' execute with "Agent don't installed".
(This is not required in SSH-connect)

Dan_Woolf

Hi @shiv03_9800,

I'm sorry for the confusion. That troubleshooting document is a bit different than what my goal was in my response. I wanted to get you to a folder that allowed you to control the permissions on that folder to remove a possible permissions issue in the Windows temp directory. I have seen on some occasions that the Windows temp directory will block deleting or modifying some existing folders. They easiest way to determine if that is the issue is to change the temp directory to a location that you can edit permissions on.

I also realize that troubleshooting document has a typo in it. The doc says to use Otter.RootPath as the element name, when you need to use OtterRootPath. Can you please confirm which element name you added to the Inedo Agent config?

Can you please clarify what you are referring to when you say that you need to reconfigure Otter to blank the temporary directory. The Inedo Agent based servers do not have an option to set a temporary path directly in Otter.

Thanks,
Dan

rhessinger

Hi @shiv03_9800,

Would you be able to send over the full execution log from running the "PowerShellDemo"?

Thanks,
Rich

shiv03_9800

Hi,

@Dan_Woolf:
<OtterRootPath>C:\ForInedoAgent</OtterRootPath>
I tried both options yesterday - with a dot and without a dot, and together at once.

Can you please clarify what you are referring to when you say that you need to reconfigure Otter to blank the temporary directory. The Inedo Agent based servers do not have an option to set a temporary path directly in Otter.

Please, look [EDO-7988]

@rhessinger: [EDO-7988]

rhessinger

Hi @shiv03_9800,

Thanks for sending that over. We have located the issue and we are working to fix it. I will let you know as soon as we have a fix.

Thanks,
Rich

shiv03_9800

docker otter:3.0.13 (wo reinstall InedoAgent), exec PowerShellDemo.
Status: Warning
(Execution: OK)
Cleanup & Finalization:
DEBUG: Cleaning up temporary files on Inedo Agent (v??, 10.72.14.141:80)...
WARN: Unable to delete temporary directory "C:\ForInedoAgent\10.72.14.130\Temp_E1104" on Inedo Agent (v??, 10.72.14.141:80): Could not load file or assembly 'System.Private.CoreLib' or one of its dependencies. The system cannot find the file specified.

gdivis

Hi @shiv03_9800,

We've now fixed this issue as well. It is logged as OT-439, and will be included in the v3.0.14 release. If you would like to try the fix right now, you can use the inedo/otter:3.0.14-ci.1 Docker image.

Thanks,
-Greg

shiv03_9800

@shiv03_9800 said in Docker Otter 3.0.12 with InedoAgent The agent does not have a valid execution temp path:

You retold:
https://docs.inedo.com/docs/inedoagent-configuration-troubleshooting
But in both cases, it is missed workaround that here need to reconfigure in Otter the 'serverX' (pull the settings), for push content to blank temporary directory.
Otherwise - 'droped' execute with "Agent don't installed".
(This is not required in SSH-connect)

docker otter:3.0.14-ci.1 still reproduced "not documented '5. Do Otter\Servers\srvX\Details\Edit\OK'".

shiv03_9800

@gdivis Thank you very much (it works).