After much trial and error I solved my problem and thought it worth posting here...

To allow a maximum of 5 retries separated by 30 seconds use the following options in the relevant systemd service file.

    [Unit]
    StartLimitInterval=200
    StartLimitBurst=5
    [Service]
    Restart=always
    RestartSec=30
    
This worked for me for a service that runs a script using &#39;Type=idle&#39;. Note that &#39;StartLimitInterval&#39; must be greater than &#39;RestartSec * StartLimitBurst&#39; otherwise the service will be restarted indefinitely.


I am debugging a Python (`3.5`) program with PyCharm (`PyCharm Community Edition 2016.2.2 ; Build #PC-162.1812.1, built on August 16, 2016 ; JRE: 1.8.0_76-release-b216 x86 ; JVM: OpenJDK Server VM by JetBrains s.r.o`) on Windows 10.

**The problem: when stopped at some breakpoints, the Debugger window is stuck at &quot;Collecting data&quot;, which eventually timeout.** (with *Unable to display frame variables*)

The data to be displayed is neither special, nor particularly large. It is somehow available to PyCharm since a conditional break point on some values of the said data works fine (the program breaks) -- it looks like the process to gather it for display only (as opposed to operational purposes) fails.

When I step into a function around the place I have my breakpoint, its data is displayed correctly. When I go up the stack (to the calling function, the one I stepped down from and where I wanted initially to have the breakpoint) - I am stuck with the &quot;Collecting data&quot; timeout again.

There have been numerous issues raised with the same point since at least 2005. Some were fixed, some not. The fixes were usually updates to the latest version (which I have).

**Is there a general direction I can go to in order to fix or work around this family of problems?**

---

EDIT: a year later the problem is still there and there is still no reaction from the devs/support after the bug was raised.

---

**EDIT April 2018: It looks like the problem is solved in the 2018.1 version**, the following code which was hanging when setting a breakpoint on the `print` line now works (I can see the variables):

    import threading
    
    def worker():
        a = 3
        print(&#39;hello&#39;)
    
    threading.Thread(target=worker).start()

Debugger times out at &quot;Collecting data...&quot;

I know you can deploy automatically to heroku from github, but I haven&#39;t found a way to only push a subfolder from github to heroku.

From the command-line I know it is possible to do this with:

    git subtree push --prefix &lt;subfolder&gt; heroku master

However, I would like to know if there is a way to use the github integration with heroku to make it pull a specific subfolder automatically when a commit is added to a branch.

Automated heroku deploy from subfolder

I want systemd to start a script and retry a maximum of 5 times, 30s apart.
Reading the systemd.service manual and searching the Internet didn&#39;t produce any obvious answers.

How to set up a systemd service to retry 5 times on a cycle of 30 seconds

<p>I want systemd to start a script and retry a maximum of 5 times, 30s apart.
Reading the systemd.service manual and searching the Internet didn't produce any obvious answers.</p>


I want to put all my functions that talk to the server and fetch data into a single reusable file in VueJS.

Plugins don&#39;t seem to be the best alternative. Template less components..?



What&#39;s the equivalent of Angular Service in VueJS?

I always run my Apache server in this way:

    sudo service apache2 start

But in many guides I saw commands like this:

    sudo systemctl start apache2

Can somebody shortly write the difference between these commands and give me advice about what command I should use in everyday work?

Difference between Systemctl and service command

I am using `Service` Class on the Android O OS. 

I plan to use the `Service` in the background. 

The [Android documentation][1] states that 

&gt; If your app targets API level 26 or higher, the system imposes restrictions on using or creating background services unless the app itself is in the foreground. If an app needs to create a foreground service, the app should call `startForegroundService()`.

If you use `startForegroundService()`, the `Service` throws the following error.

```none
Context.startForegroundService() did not then call
Service.startForeground() 
```

What&#39;s wrong with this?


  [1]: https://developer.android.com/guide/components/services#StartingAService

Context.startForegroundService() did not then call Service.startForeground()

After upgrading my phone to 8.1 Developer Preview my background service no longer starts up properly.

In my long-running service I&#39;ve implemented a `startForeground` method to start the ongoing notification which is called in on create.

    @TargetApi(Build.VERSION_CODES.O)
    private fun startForeground() {
        // Safe call, handled by compat lib.
        val notificationBuilder = NotificationCompat.Builder(this, DEFAULT_CHANNEL_ID)

        val notification = notificationBuilder.setOngoing(true)
                .setSmallIcon(R.drawable.ic_launcher_foreground)
                .build()
        startForeground(101, notification)
    }

Error message:

    11-28 11:47:53.349 24704-24704/$PACKAGE_NAMEE/AndroidRuntime: FATAL EXCEPTION: main
        Process: $PACKAGE_NAME, PID: 24704
        android.app.RemoteServiceException: Bad notification for startForeground: java.lang.RuntimeException: invalid channel for service notification: Notification(channel=My channel pri=0 contentView=null vibrate=null sound=null defaults=0x0 flags=0x42 color=0x00000000 vis=PRIVATE)
            at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1768)
            at android.os.Handler.dispatchMessage(Handler.java:106)
            at android.os.Looper.loop(Looper.java:164)
            at android.app.ActivityThread.main(ActivityThread.java:6494)
            at java.lang.reflect.Method.invoke(Native Method)
            at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

`invalid channel for service notification`, apparently my old channel the `DEFAULT_CHANNEL_ID` is no longer appropriate for API 27 I assume. What would be the proper channel? I&#39;ve tried to look through the documentation 

startForeground fail after upgrade to Android 8.1

Hi I&#39;m trying to see the status of my apache services on my Mac. I tried the command 

    sudo service httpd status

but command not found

I look up in Google and discover `systemctl` so I try that

    sudo man systemctl

and it shows no manual entry for `systemctl`

I noticed that I didn&#39;t see much mac os and only see linux in the websites on Google.

Does the command `systemctl` and `service` exists on linux only and not Mac?

If so, what is the mac version of these command?


Does the command systemctl and service exists on linux only and not mac?

I am using a systemd service which calls a process when it&#39;s been &quot;started&quot; (e.g. `systemctl start test.service`). As per the design, the process stays for ever in a loop, we are able to see process existence using &#39;ps&#39; command. We have also seen that the process is getting killed (as intended) for `systemctl stop` command. 
However our requirement is, we want to do some safe shutdown operations from within the process before it gets killed. But I am not sure how to detect a systemd stop operation from within the process. 

Does a `systemctl stop test.service` command send `SIGKILL` or `SIGTERM` signal to kill the process? How can I detect a `systemctl stop` operation from within a process? 

How systemd stop command actually works

I am having a service that depends on Cassandra coming up gracefully and the cluster being up and ready.

To ensure that the dependency order is met, I have the following unit file 

    [Unit]
    Requires=cassandra.service
    After=cassandra.service
    
    [Service]
    Environment=JAVA_HOME=/usr/java/jre
    ExecStart=@bringup.instance.path@/webapps/bringup-app/bin/bringup
    TimeoutStartSec=0
    ExecStop=
    PIDFile=@bringup.instance.path@/logs/bringup.pid
    Restart=always
    
    [Install]
    WantedBy=multi-user.target

How do I ensure that the bringup-app process waits for 30 seconds before it attempts to start up?  Currently although it is started after Cassandra, I have noticed that the Cassandra cluster is not up yet and hence any attempt from the bringup-app to connect to Cassandra as part of startup fails. 

I therefore want to add a delay. Is that possible via the unit file?

How to ensure that there is a delay before a service is started in systemd?

I&#39;m trying to set up a simple systemd timer to run a bash script every day at midnight.

```systemctl --user status backup.service``` fails and logs the following:

    backup.service: Failed at step EXEC spawning /home/user/.scripts/backup.sh: No such file or directory.

    backup.service: Main process exited, code=exited, status=203/EXEC
    Failed to start backup.
    backup.service: Unit entered failed state.
    backup.service: Failed with result &#39;exit-code&#39;.

I&#39;m lost, since the files and directories exist. The script is executable and, just to check, I&#39;ve even set permissions to 777.

Some background:

The ```backup.timer``` and ```backup.service``` unit files are located in ```/home/user/.config/systemd/user```.

```backup.timer``` is loaded and active, and currently waiting for midnight.

Here&#39;s what it looks like:

    [Unit]
    Description=Runs backup at 0000

    [Timer]
    OnCalendar=daily
    Unit=backup.service

    [Install]
    WantedBy=multi-user.target

Here&#39;s ```backup.service```:

    [Unit]
    Description=backup

    [Service]
    Type=oneshot
    ExecStart=/home/user/.scripts/backup.sh

    [Install]
    WantedBy=multi-user.target

And lastly, this is a paraphrase of ```backup.sh```:
    
    #!/usr/env/bin bash

    rsync -a --delete --quiet /home/user/directory/ /mnt/drive/directory-backup/

The script runs fine if I execute it myself.

Not sure if it matters, but I use ```fish``` as my shell (started from .bashrc).

I&#39;m happy to post the full script if that&#39;s helpful.

Fixing a systemd service 203/EXEC failure (no such file or directory)

Is it possible to create service with the same script started with different input parameters?

Example:

    [Unit]
    Description=script description
    
    [Service]
    Type=simple
    ExecStart=/script.py parameters1
    ExecStart=/script.py parameters2
    Restart=on-failure
    
    [Install]
    WantedBy=multi-user.target

Is it possible? 

Will it be launched in serial-mode? Or in two different process?

Systemd with multiple execStart

I have an issue with a systemd config for ElasticSearch.

    [Unit]
    Description=platform-elasticsearch
    After=syslog.target network.target remote-fs.target nss-lookup.target
    
    [Service]
    User={{ app_user }}
    Group={{ app_group }}
    Environment=ES_PATH_CONF=/platform/opt/elasticsearch-{{ elasticsearch.version }}/config
    Environment=JAVA_HOME=/platform/opt/jdk{{ jdk.major_version }}_{{ jdk.minor_version }}
    LimitAS=infinity
    LimitRSS=infinity
    LimitCORE=infinity
    LimitNOFILE=100000
    LimitMEMLOCK=100000
    StandardOutput=syslog
    StandardError=syslog
    WorkingDirectory=/platform/var/app/elasticsearch
    ExecStart=/platform/opt/elasticsearch-{{ elasticsearch.version }}/bin/elasticsearch
    ExecReload=/bin/kill -s HUP $MAINPID
    ExecStop=/bin/kill -s -TERM $MAINPID
    TimeoutStopSec=60
    # When a JVM receives a SIGTERM signal it exits with code 143
    SuccessExitStatus=143 0
    Type=simple
    Restart=on-failure
    RestartSec=10
    PIDFile=/platform/var/run/elasticsearch.pid
    
    [Install]
    WantedBy=multi-user.target

This does not seem to let me configure the vm.max_map_count setting.

    Jul 20 14:53:46 scratchpad elasticsearch: [2018-07-20T14:53:46,359][INFO ][o.e.b.BootstrapChecks    ] [1oQJNUK] bound or publishing to a non-loopback     address, enforcing bootstrap checks
    Jul 20 14:53:46 scratchpad elasticsearch: ERROR: [1] bootstrap checks failed
    Jul 20 14:53:46 scratchpad elasticsearch: [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
    Jul 20 14:53:46 scratchpad elasticsearch: [2018-07-20T14:53:46,376][INFO ][o.e.n.Node               ] [1oQJNUK] stopping ...
    Jul 20 14:53:46 scratchpad elasticsearch: [2018-07-20T14:53:46,414][INFO ][o.e.n.Node               ] [1oQJNUK] stopped
    Jul 20 14:53:46 scratchpad elasticsearch: [2018-07-20T14:53:46,414][INFO ][o.e.n.Node               ] [1oQJNUK] closing ...
    Jul 20 14:53:46 scratchpad elasticsearch: [2018-07-20T14:53:46,445][INFO ][o.e.n.Node               ] [1oQJNUK] closed
    Jul 20 14:53:46 scratchpad systemd: platform-elasticsearch.service: main process exited, code=exited, status=78/n/a

The specific issue is the following:

    Jul 20 14:53:46 scratchpad elasticsearch: [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]


I have been able to start elastic search on the commandline with the following:

    sudo su -c &#39;echo 262144 &gt; &quot;/proc/sys/vm/max_map_count&quot;&#39; &amp;&amp; \ 
    export JAVA_HOME=/platform/opt/jdk1.8.0_181 &amp;&amp; \
    export ES_PATH_CONF=/platform/opt/elasticsearch-6.3.1/config &amp;&amp; \
    /platform/opt/elasticsearch-6.3.1/bin/elasticsearch 

can anyone tell me why LimitMEMLOCK=100000 does not work, and how I can effectively set max_map_count from within systemd.

I have also tried to set the following:

    cat /etc/security/limits.d/30_elastic_limits.conf

    vagrant       hard    nofile     500000
    vagrant       hard    memlock     262144

but this seems to be totally ignored by systemd.

Content Type	Original Author	Original Content on Stackoverflow
Question	jross	View Question on Stackoverflow
Solution 1 - Service	jross	View Answer on Stackoverflow

How to set up a systemd service to retry 5 times on a cycle of 30 seconds

Service Problem Overview

Service Solutions

Solution 1 - Service

Automated heroku deploy from subfolder

Debugger times out at "Collecting data..."

Attributions