immense / immense/Remotely

Remotely_Server_Installer Unhandled Exception after successful build

Open
#379 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
5.1k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

I have the same error #276 but with the lastest release

After successfully finishishing the build action on github the script stops with an unhandled exception

Directory: /var/www/remotely/

Get artifacts response status code: OK

Trigger GitHub Actions build.

Dispatch response status code: NoContent

Build action triggered successfully.  Waiting for build
completion.

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Waiting for GitHub build completion.

Get artifacts response status code: OK

Downloading build artifact.

Download artifact response status code: OK

Extracting files.

Launching install script for selected reverse proxy type.

Unhandled exception. System.ComponentModel.Win32Exception (2): No such file or directory
   at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
   at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(String fileName, String arguments)
   at Server.Installer.Services.ServerInstaller.LaunchExternalInstaller(CliParams cliParams)
   at Server.Installer.Services.ServerInstaller.PerformInstall(CliParams cliParams)
   at Server.Installer.Program.Main(String[] args)
   at Server.Installer.Program.<Main>(String[] args)
Aborted

To Reproduce

Tested on Ubuntu 20.04

Steps to reproduce the behavior:

  • execute ./Remote_Server_Installer
  • Make sure to select true when asked for new build
  • wait for the build to be done
  • See error

Remotely Version
Server: Current release v2021.08.26.1335

Expected Behavior

Fully execute the setup procedure

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at Server.Installer.Services.ServerInstaller.LaunchExternalInstaller, called by PerformInstall and Program.Main, and inspect the external installer process launched after artifact extraction. Reproduce with ./Remote_Server_Installer on Ubuntu 20.04 using a new build, then verify that the setup procedure completes instead of raising the reported Win32Exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.