Problem:
After upgrade of smart-proxy 3.12 to 3.13 on a Windows server following install instructions at Foreman :: Manual, the win-service.log shows the following error after attempting to start the “Foreman Smart Proxy” service:
Did you mean? Logging C:/smart-proxy-3.13-stable/lib/proxy/log_buffer/buffer.rb:42:in `initialize’
Note: we are using Ruby 2.7 and its associated devkit. We did not experience any error when previously upgrading from 3.11 to 3.12.
Expected outcome:
Service should start without errors.
Foreman and Proxy versions:
3.13.1
Foreman and Proxy plugin versions:
Distribution and version:
Windows server 2019 Version 1809
Other relevant data:
win-service.log
2025-04-10 10:25:52 -0500 Daemon failure: uninitialized constant Logger
Did you mean? Logging C:/smart-proxy-3.13-stable/lib/proxy/log_buffer/buffer.rb:42:in initialize' C:/smart-proxy-3.13-stable/lib/proxy/log_buffer/buffer.rb:34:in new’
C:/smart-proxy-3.13-stable/lib/proxy/log_buffer/buffer.rb:34:in instance' C:/smart-proxy-3.13-stable/lib/proxy/log_buffer/decorator.rb:12:in initialize’
C:/smart-proxy-3.13-stable/lib/proxy/log_buffer/decorator.rb:6:in new' C:/smart-proxy-3.13-stable/lib/proxy/log_buffer/decorator.rb:6:in instance’
C:/smart-proxy-3.13-stable/lib/proxy/log.rb:8:in logger' C:/smart-proxy-3.13-stable/lib/launcher.rb:148:in rescue in launch’
C:/smart-proxy-3.13-stable/lib/launcher.rb:126:in launch' C:/smart-proxy-3.13-stable/bin/smart-proxy-win-service:28:in service_main’
C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/win32-service-2.3.2/lib/win32/daemon.rb:321:in mainloop' C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/win32-service-2.3.2/lib/win32/daemon.rb:211:in mainloop’
C:/smart-proxy-3.13-stable/bin/smart-proxy-win-service:39:in `’
Our workaround was to add require 'logger' at the very top of the file C:/smart-proxy-3.13-stable/lib/proxy/log_buffer/buffer.rb.
Could someone advise if there is a better way to resolve this issue?