Foreman start script - background

I'm facing an issue with my Foreman script. I've installed it following the installation path from Descartes article in GitHub (https://github.com/obfuscurity/descartes). The scripts functions great but I have two things going on.
1- How can I run it in background mode?
2- After a while the service will fall without any apparent reason.
$ cd /descartes_folder/
$ foreman start
13:12:43 web.1 | started with pid 3011
13:12:46 web.1 | >> Thin web server (v1.5.1 codename Straight Razor)
13:12:46 web.1 | >> Maximum connections set to 1024
13:12:46 web.1 | >> Listening on 0.0.0.0:5000, CTRL+C to stop
I tried to send its output to a log file, but the only I got was:
19:30:11 system | sending SIGTERM to all processes
19:30:11 web.1 | exited with code 0
Like if there was a CTRL+C.
Any ideas? anything would be really appreciated!
Thanks!

I just gave up on Foreman. No answer from any of the portals, forums, google groups..even I tried to contact the guy who wrote it directly, still nothing. Finally got another web console for my Graphite metrics (dashboard) and discarded Descartes (the one requiring Foreman).
Thanks anyway!

Related

Convox CLI deploy gives 502 response

I'm suddenly having issues deploying my apps to AWS ECS using the Convox CLI. When I am trying as of Friday, this is what happens:
$ convox deploy -a my-app -r test
Packaging source... OK
Uploading source... OK
Starting build... ERROR: response status 502
This is regardless of rack, and other operations such as "env" and "logs" seem to work. I don't know how to go about trouble shooting this. Is there some switch I can use to get more debug info from the CLI? I am assuming the "502" is an HTTP error code, but I do not know where it is coming from. I've looked around in AWS, but can not seem to find any errors there (however, is not sure where to look).
Any help would be appreciated.
Had the same problem on a rack running a version from 2019. Solved this updating the rack to version 20211019100155 as Brian suggested.

qdbus is Segmentation faulting

I'm using KTimeTracker to monitor my time on different projects. I have a PHP script that periodically runs to give me an idea on how long I've worked in the day.
The PHP script used to connect to KtimeTracker using qdbus to save to file and then use qdbus to
export the CSV file.
For those that wonder why I'm bothering with this setup, I work from home and need to monitor my time to ensure I'm working the right number of hours.
The script worked perfectly well for quite a while but has recently started failing when using qdbus. The simplest call to qdbus is :
qdbus org.kde.ktimetracker /KTimeTracker saveAll
The result of this is
Segmentation fault (core dumped)
qdbus org.kde.ktimetracker /KTimeTracker
Segmentation fault (core dumped)
qdbus org.kde.ktimetracker
/KTimeTracker
/MainApplication
/ktimetracker
/ktimetracker/MainWindow_1
/ktimetracker/MainWindow_1/actions
/ktimetracker/MainWindow_1/actions/file_open
/ktimetracker/MainWindow_1/actions/file_save
/ktimetracker/MainWindow_1/actions/options_configure
/ktimetracker/MainWindow_1/actions/start_new_session
/ktimetracker/MainWindow_1/actions/edit_history
/ktimetracker/MainWindow_1/actions/reset_all_times
/ktimetracker/MainWindow_1/actions/start
/ktimetracker/MainWindow_1/actions/stop
/ktimetracker/MainWindow_1/actions/focusSearchBar
/ktimetracker/MainWindow_1/actions/stopAll
/ktimetracker/MainWindow_1/actions/focustracking
/ktimetracker/MainWindow_1/actions/new_task
/ktimetracker/MainWindow_1/actions/new_sub_task
/ktimetracker/MainWindow_1/actions/delete_task
/ktimetracker/MainWindow_1/actions/edit_task
/ktimetracker/MainWindow_1/actions/edit_task_time
/ktimetracker/MainWindow_1/actions/mark_as_complete
/ktimetracker/MainWindow_1/actions/mark_as_incomplete
/ktimetracker/MainWindow_1/actions/export_dialog
/ktimetracker/MainWindow_1/actions/import_planner
/ktimetracker/MainWindow_1/actions/searchbar
/ktimetracker/MainWindow_1/actions/file_quit
/ktimetracker/MainWindow_1/actions/options_configure_keybinding
/ktimetracker/MainWindow_1/actions/options_show_statusbar
/ktimetracker/MainWindow_1/actions/options_configure_toolbars
/org
/org/kde
/org/kde/ktimetracker
I'm sure that I'm missing something simple but just can't see it. I've spent a few hours already Googling but have come up with nothing.
I don't know if these are of any value
sudo zypper search --provides qdbus
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+------------------------+--------------------------------------------------+--------
i+ | libqt5-qdbus | Command line client for communication over D-Bus | package
| libqt5-qdbus-debuginfo | Debug information for package libqt5-qdbus | package
i+ | libqt5-qttools | Qt 5 QtTools Module | package
cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20201114"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
...
develop#bambam:~> bash --version
GNU bash, version 5.0.18(1)-release (x86_64-suse-linux-gnu)
...
Any help will be appreciated.
Cheers
replace qdbus command with qdbus-qt5

Is there a way to see a list of stopped VM instances in IBM Cloud?

To clean up, I want to see what VM instances have been stopped but not terminated. I don't think there is any policy that will terminate them automatically, and I cannot find a way to see how long the instances have been stopped. I am just working from documentation, though, so anyone with practical experience might be able to offer some advice.
If you are looking for a CLI command, IBM Cloud CLI has an infrastructure-service plugin to help you see the instance information. The instructions to set up the plugin can be found in this solution tutorial
ibmcloud is instances
You can use grep with the command to see the instances that are stopped
ibmcloud is instances | grep `stopped`
To get the ID of the stopped VM, run the following command
ibmcloud is instances | grep 'stopped' | awk '{print $1}'

ConEmu stopped working with Bash on Windows

I have been using ConEmu for some time to run 'bash for windows', but all of the sudden it stopped working. When I launch a bash tab it now says:
ConEmuC: Root process was alive less than 10 sec, ExitCode=0.
Press Enter or Esc to close console...
I think this means that it launched something, but the shell closed quickly. I haven't changed anything that I can recall with the system, it just started doing that.
Windows version: 10 (build 15063)
ConEmu version: 180626 preview
No windows updates were done recently.
If I launch 'Bash on Ubuntu on Windows' from the start bar, it works fine (but I prefer using conemu as a terminal). Also, I can launch a cmd tab in conemu, then type bash and the bash shell will start. Unfortunately, launching bash in this way results in a lack of mouse support, and strange arrow key behavior.
I am at a bit of a loss. It worked perfectly previously... then it just stopped. Any help on how to debug or fix this would be appreciated.
If anybody finds this with a similar problem, my solution was to make a new task in ConEmu, with the command:
%windir%\system32\bash -l -i -cur_console:p5
The key is the -cur_console:p5, which sets the pty type as:
p[N] - pty modes, N - bitmask: 1 - XTermKeys, 2 - BrPaste, 4 - AppCursorKeys; default is 5 (1+4)
For some reason, setting p5 is necessary for me, despite it being listed as the default. Still not sure what changed, but at least it is working now.
I have the same problem but (for what it's worth) found that when it happens (varying between intermittent and incessant) restarting my machine fixes the issue every time.

Cpanel - There is another upcp process running

I have this error when i try to use cpanel upgrade to new version
There is another upcp process running, and you are watching the log from the existing process.
And then in box i see
Unable to find log file: /var/cpanel/updatelogs/last
please help how can i terminate as ps aux | grep upcp shows no process running. I also have deleted update_in_progress.txt from /usr/local/cpanel. I am able to access tweak settings but not able to upgrade. Also tried upcp --force. Please help
If /scripts/upcp --force is not working, then I think your best option is to reboot the server and run it again.