# Getting error while run the yocto pipeline script in jenkins **URL:** \ **Category:** Using Jenkins\ **Tags:** question\ **Created:** [July 20, 2023, 6:42am UTC](https://community.jenkins.io/t/getting-error-while-run-the-yocto-pipeline-script-in-jenkins/8567 "2023-07-20T06:42:50Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![adlink](https://avatars.discourse-cdn.com/v4/letter/a/97f17d/32.png) [@adlink](https://community.jenkins.io/u/adlink)\ **Post date:** [July 20, 2023, 6:42am UTC](https://community.jenkins.io/t/getting-error-while-run-the-yocto-pipeline-script-in-jenkins/8567/1 "2023-07-20T06:42:50Z")
we are getting a error :- " JENKINS-48800: if on an extremely laggy filesystem, consider \*Dorg jenkinsci.plugins.durabletask. BourneShellScript.HEARTBEAT CHECK INTER VAL=86400" while run jenkins pipeline script . ---
**Author:** ![NotMyFault](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/notmyfault/32/466_2.png) [@NotMyFault](https://community.jenkins.io/u/NotMyFault)\ **Post date:** [July 20, 2023, 8:31am UTC](https://community.jenkins.io/t/getting-error-while-run-the-yocto-pipeline-script-in-jenkins/8567/2 "2023-07-20T08:31:18Z")
As the message tells you, make sure to check [JENKINS-48300](https://issues.jenkins.io/browse/JENKINS-48300) for additional information. That’s not an error, just a pointer. ---
**Author:** ![adlink](https://avatars.discourse-cdn.com/v4/letter/a/97f17d/32.png) [@adlink](https://community.jenkins.io/u/adlink)\ **Post date:** [July 20, 2023, 9:10am UTC](https://community.jenkins.io/t/getting-error-while-run-the-yocto-pipeline-script-in-jenkins/8567/3 "2023-07-20T09:10:57Z")
we have added Dorg jenkinsci.plugins.durabletask. BourneShellScript.HEARTBEAT CHECK INTER VAL=86400 in /etc/default/jenkins on JAVA\_ARG but when i add and restart the service file the changes or not reflected , i have check with sudo cat /proc/$(pidof java)/cmdline | tr ‘\0’ ‘\n’ is there any other way to set the HEARTBEAT CHECK INTER on ubuntu jenkins ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [July 24, 2023, 1:02pm UTC](https://community.jenkins.io/t/getting-error-while-run-the-yocto-pipeline-script-in-jenkins/8567/4 "2023-07-24T13:02:51Z")
The `/etc/defauilt/jenkins` file is not used to control the Jenkins service any longer. Since the Linux installers switched to use `systemd` to control the service instead of using the System V `init` system, that file is no longer read. Jenkins 2.332.1 switched Jenkins from using System V init to use systemd with its Linux package installers for Debian, Ubuntu, Red Hat, Alma, openSUSE, Rocky, and more. The [LTS Upgrade Guide](https://www.jenkins.io/doc/upgrade-guide/2.332/#upgrading-to-jenkins-lts-2-332-1) describes that transition and how to adapt your environment to the transition. > **[Upgrading to Jenkins LTS 2.332.x](https://www.jenkins.io/doc/upgrade-guide/2.332/#upgrading-to-jenkins-lts-2-332-1)** > > Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software There is a [blog post](https://www.jenkins.io/blog/2022/03/25/systemd-migration/) about it as well at > **[Linux installation packages migrated from System V init to systemd](https://www.jenkins.io/blog/2022/03/25/systemd-migration/)** > > Starting with Jenkins 2.335, the Jenkins project is migrating from System V init to systemd. There is also a [video introduction](https://www.youtube.com/watch?v=MkokjTQ2ngc) for RPM based distributions like Red Hat Enterprise Linux, Alma Linux, Rocky Linux, Oracle Linux, and Amazon Linux. [![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/5/5d731f86134683079a41351908d8832c01e0a6f4.jpeg "🔴 Managing the Jenkins systemd Service on CentOS 7.9") ](https://www.youtube.com/watch?v=MkokjTQ2ngc) There is also a [video introduction](https://www.youtube.com/watch?v=pwR9TPW2oG4) for deb based distributions like Debian and Ubuntu [![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/0/04a2972bcb9f7e4756fdc406b9992a75a8f47ed2.jpeg "🔴 Managing the Jenkins systemd Service on Ubuntu 20.04") ](https://www.youtube.com/watch?v=pwR9TPW2oG4) ---
**Author:** ![adlink](https://avatars.discourse-cdn.com/v4/letter/a/97f17d/32.png) [@adlink](https://community.jenkins.io/u/adlink)\ **Post date:** [July 25, 2023, 3:15pm UTC](https://community.jenkins.io/t/getting-error-while-run-the-yocto-pipeline-script-in-jenkins/8567/5 "2023-07-25T15:15:20Z")
i have set the [Service] Environment=“JAVA\_OPTS=-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT\_CHECK\_INTERVAL=86400” on jenkins service file , but this time the jenkins came out from the yocto build to the login prompt when i enter the user name and password then the build is restarted but the build is running but it holds on the same place