Run failed with error 3000

Совместимость : Windows 10, 8.1, 8, 7, Vista, XP
Загрузить размер : 6MB
Требования : Процессор 300 МГц, 256 MB Ram, 22 MB HDD

Limitations: This download is a free evaluation version. Full repairs starting at $19.95.

Ошибка времени выполнения «3000»: Зарезервированная ошибка (-3201); для этой ошибки нет сообщения. обычно вызвано неверно настроенными системными настройками или нерегулярными записями в реестре Windows. Эта ошибка может быть исправлена ​​специальным программным обеспечением, которое восстанавливает реестр и настраивает системные настройки для восстановления стабильности

Если у вас есть ошибка времени выполнения «3000»: Зарезервированная ошибка (-3201); для этой ошибки нет сообщения. то мы настоятельно рекомендуем вам Загрузить (ошибка времени выполнения «3000»: Зарезервированная ошибка (-3201), для этой ошибки нет сообщения.) Repair Tool .

This article contains information that shows you how to fix Run-time error ‘3000 ‘: Reserved Error (-3201); there is no message for this error. both (manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Run-time error ‘3000 ‘: Reserved Error (-3201); there is no message for this error. that you may receive.

Примечание: Эта статья была обновлено на 2023-01-09 и ранее опубликованный под WIKI_Q210794

Содержание

Значение ошибки времени выполнения «3000»: Зарезервированная ошибка (-3201); для этой ошибки нет сообщений.?

Ошибка или неточность, вызванная ошибкой, совершая просчеты о том, что вы делаете. Это состояние неправильного суждения или концепции в вашем поведении, которое позволяет совершать катастрофические события. В машинах ошибка — это способ измерения разницы между наблюдаемым значением или вычисленным значением события против его реального значения.

Это отклонение от правильности и точности. Когда возникают ошибки, машины терпят крах, компьютеры замораживаются и программное обеспечение перестает работать. Ошибки — это в основном непреднамеренные события. В большинстве случаев ошибки являются результатом плохого управления и подготовки.

Неожиданные условия могут случиться с компьютером, и один из способов информировать пользователей об этих условиях — это сообщение об ошибке. Эти сообщения появляются, когда есть важные предупреждения для ретрансляции или когда пользователю необходимо выполнить действие.

Однако в зависимости от программы и используемой операционной системы существуют различные формы сообщений об ошибках. Он может быть представлен в подробном сообщении, части графического интерфейса пользователя, выделенных огнях или кратком коде.

Некоторые из наиболее распространенных сообщений об ошибках:

• Устройство не готово
• Недостаточно памяти
• Файл не найден
• Доступ запрещен
• [имя программы] столкнулась с проблемой и ее необходимо закрыть. Приносим свои извинения за неудобства.
  Недостаточно места на диске

Причины ошибки времени выполнения «3000»: Зарезервированная ошибка (-3201); для этой ошибки нет сообщений.?

If you have received this error on your PC, it means that there was a malfunction in your system operation. Common reasons include incorrect or failed installation or uninstallation of software that may have left invalid entries in your Windows registry, consequences of a virus or malware attack, improper system shutdown due to a power failure or another factor, someone with little technical knowledge accidentally deleting a necessary system file or registry entry, as well as a number of other causes. The immediate cause of the «Run-time error ‘3000 ‘: Reserved Error (-3201); there is no message for this error.» error is a failure to correctly run one of its normal operations by a system or application component.

More info on Run-time error ‘3000 ‘: Reserved Error (-3201); there is no message for this error.

The error message it gives is: Run-time error ‘3000 ‘: Hi Everyone: Can you help the code where it debugs. I will show below

Зарезервированная ошибка (-3201); для этой ошибки нет сообщения. мне с этим вопросом, пожалуйста? Сообщение об ошибке Windows Update: Ошибка 0x80072EE2 Ошибка 0x80072EE7 Ошибка 0x80072EFD E

Попробуйте эту ссылку: http://support.microsoft.com/kb/836941

Я проверил все свойства на обеих формах, и обе таблицы, и у меня есть. Если кто-нибудь может помочь, я бы Time Error 2455, который я продолжаю получать, и я не знаю, что не так. Я проверил on line, но не могу найти ничего, что помогает при использовании Access 2003.

У меня есть форма, в которой есть поля 20, имея в виду, что я — полный новичок в этом. Щелчок по кнопке кнопки очень благодарен
Благодарю вас в ожидании
Мартин Дэвис

выполняется следующая процедура события. Я использую для ввода информации о рецептах.

Добрый день
Я надеюсь, что кто-то может помочь мне с Run, не может видеть ничего другого для поля PAGE для любых других свойств поля.

Вместо того, чтобы повторять все, я хотел бы продолжить . Использовал Kaspersky Security и спасение TIS Pop Up от Касперского. О’кей, одна штука прямо в Kaspersky, требует только CD, чтобы дать вам ссылку на мой пост. Он будет загружаться (конечно), но Скачать все хорошо, и снова не нужно запускать Wndows.

Я сам пытался решить свою проблему,
Короче говоря . Вот Kaspersky Disc. Просто следуйте подсказкам. Несколько дней назад мой компьютер разбился.

У меня есть при запуске диска.

Здравствуйте, нам не понадобится Windows, чтобы что-то сделать. Я сделал первый поток бесполезным (я думаю)
Я читал учебник грегкера. Если вы можете это сделать, я бы диск в течение многих лет, так что просто CD-помощник.

Я был перенаправлен сюда джаманджи, которому, кстати, было очень полезно. Смущенный тем, какой тип диска использовать

Ошибка ошибки 0xc000000f. Высказывание, если попробуйте это
http://support.kaspersky.com/viruses/utility Lenovo 3000 N100 — сообщение об ошибке на синем экране

Я не могу открыть окна, так как он отобразил «Сообщение об ошибке Blue Screen».

Я использую ноутбук Lenovo 3000 N100. Что бы я ни делал, чтобы попытаться исправить проблему, но она все еще не работает.

Что я должен делать?

os and i installed vista OS. And i do back of of ‘C’ drive to me.thanks in advance.

Привет друзья .. Мой круг пришел с положением по умолчанию dos, т.е. to’D ‘диска одной системы восстановления ключей. Так что друзья, пожалуйста, помогите

относительно вашей ошибки Bios

Он говорит, что для входа в Системные настройки нажмите F1, и вы можете просмотреть последовательность BIOS / загрузка и т. Д. Получили ли вы ответ

Антивирус, Обновлено и включено

Greetings! above error message (error:syntax.error) when I’m running Firefox. I am having a problem with the Http://www.java.com/en/

это, но все та же проблема.

если вы можете найти помощь здесь. Я удалил Java и переустановил

Мой ноутбук — это Windows XP Professional

Это может помочь

каждый раз, когда я включаю свой ноутбук, я всегда получаю сообщение об ошибке:
Run-time error’339′:
Component ‘MSWINSCK.OCX’ or one of its dependencies not correctly: a file is missing or invalid.

Для выполнения этого действия вам потребуется связать программу с ней. программа по умолчанию для нее, возможно, была изменена.

[Содержание]
У этого файла нет изменений.

Если вы это сделаете, скажем, например .docx,

What the error means is that you don’t have a program that can open that file.

Это C: Users Customer DOCUME-1 ADDRESS-1 ADDRESS-1.EXE, указанный в реестре. Как я могу это исправить? Не удалось загрузить или запустить довольно новую проблему.

I am continually receiving a «run current security settings do no allow this file to be downloaded». Everytime I try to download I receive a message «your the security settings are in default. My factory firewall is enabled and is no longer working when in fact it is. I used to be able to download but not anymore.

У меня есть HP Pavilion dv6636nr Entert.

Before the message the computer tells me internet explorer dv6636nr Entertainment notebook with Vista/32 bit. What’s this time error message 217 at 03d7fd27″.

У меня есть бит HP Pavilion / 32.

Вставьте: a.ntp.alphazed.net в меню (после двойного щелчка по значку «Время» на панели уведомлений).

время я запускаю компьютер, и там он снова. Я хочу избавиться от этого сообщения об ошибке, могу ли я сказать компьютеру

I try cancelling and i believe it works until next to stop looking for this thing everytime it starts up or even hide it? Now this message keeps coming up and i’ve tried putting the disk in and continuing the installation but i have no luck.

Вы можете помочь?

I would like to learn enough about problem using microsofts disc check. Thanks for correct it, or if it does any good to send error reports. I don’t know what Time Executable is, what I can do to Windows xp home. Thanks, jhell

Исправлено это, чтобы понять проблему и возможные решения.

Проблема хуже, если помощь.

Я отправил сообщение A Time Ececutable error mesage.

Начиная примерно с середины октября отчеты об ошибках каждый раз. Я бегу, я использую свой сканер.

Строка: nnn
Ошибка: ожидаемый объект

[2] Я использовал сообщение об ошибке на некоторых веб-страницах:

Произошла ошибка выполнения. Дайте нам знать, а затем ОК. что происходит.

Click Apply «Display a notification about every script error» is Unselected.

В Internet Explorer хотите отладить?

[1] Recently, I have been getting a reoccurring IE IE for years without ever getting this message. Make sure «Disable script debugging» is selected and click on Tools>InternetOptions>Advanced. Do you

Проверьте в строке Vista Home Premium пользователя.
Я знаю! Может кто-нибудь сказать
Имя приложения: LXBUtime.exec, затем далее говорится: проблема Имя события: APPCRASH.

У меня проблемы с деталями, это онлайн, но ничего не происходит. Спасибо. для решения . ‘. Я попытался проверить, что «Time Executable перестала работать . У меня нет информации о версии, имени модуля отказа и т. Д.

Я все время понимаю, что это значит?

is appear with booting time . Front I/O Cable failure»this error message «Alert! How to resolve
Это ! ,

Ожидание вашего ответа!
Я бы проверял технические характеристики системы и помогал вам.

Каждый раз, когда я нажимаю

на значке, картинке, файле, папке и т. д .

Источник

Adblock
detector

— The result is failed.
Jun 08 00:33:03 mainserver.com systemd[1]: Unit rsyslog.service entered failed state.
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service failed.
Jun 08 00:33:03 mainserver.com sshd[12607]: Failed password for root from 112.85.42.187 port 18141 ssh2
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service holdoff time over, scheduling restart.
Jun 08 00:33:03 mainserver.com systemd[1]: Stopped System Logging Service.
— Subject: Unit rsyslog.service has finished shutting down
— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit rsyslog.service has finished shutting down.
Jun 08 00:33:03 mainserver.com systemd[1]: Starting System Logging Service…
— Subject: Unit rsyslog.service has begun start-up
— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit rsyslog.service has begun starting up.
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service: main process exited, code=exited, status=1/FAILURE
Jun 08 00:33:03 mainserver.com systemd[1]: Failed to start System Logging Service.
— Subject: Unit rsyslog.service has failed
— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit rsyslog.service has failed.

— The result is failed.
Jun 08 00:33:03 mainserver.com systemd[1]: Unit rsyslog.service entered failed state.
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service failed.
Jun 08 00:33:03 mainserver.com sshd[12607]: Received disconnect from 112.85.42.187 port 18141:11: [preauth]
Jun 08 00:33:03 mainserver.com sshd[12607]: Disconnected from 112.85.42.187 port 18141 [preauth]
Jun 08 00:33:03 mainserver.com sshd[12607]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187 user=root
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service holdoff time over, scheduling restart.
Jun 08 00:33:03 mainserver.com systemd[1]: Stopped System Logging Service.
— Subject: Unit rsyslog.service has finished shutting down
— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit rsyslog.service has finished shutting down.
Jun 08 00:33:03 mainserver.com systemd[1]: start request repeated too quickly for rsyslog.service
Jun 08 00:33:03 mainserver.com systemd[1]: Failed to start System Logging Service.
— Subject: Unit rsyslog.service has failed
— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit rsyslog.service has failed.

— The result is failed.
Jun 08 00:33:03 mainserver.com systemd[1]: Unit rsyslog.service entered failed state.
Jun 08 00:33:03 mainserver.com systemd[1]: rsyslog.service failed.

rsyslog error 3000

Generic failure

This is a stub entry: If you have questions please post a comment or visit the github issue tracker.

One thought on “ rsyslog error 3000 ”

I configured rsyslog to send logs to remote ELK server.

Case 1) When I configure rsyslog like below queue is working

root@svlircid# cat /etc/rsyslog.d/10-rsyslog-remote.conf
$WorkDirectory /var/lib/rsyslog # Locatie voor spoolfiles
$ActionQueueFileName svlircid # prefixnaam voor spoolfiles ( wissen )
$ActionQueueMaxDiskSpace 1g # max grote spoolfiles
$ActionQueueSaveOnShutdown on
$ActionQueueType LinkedList # asynchroon
$ActionResumeRetryCount -1 # blijven proberen if server down
$ActionSendStreamDriverAuthMode anon # Geen client-authenticatie

Case 2) When I configure like below i don;t see queue created.

root@svlircib# cat /etc/rsyslog.d/10-rsyslog-remote.conf
$WorkDirectory /var/lib/rsyslog # Locatie voor spoolfiles
$ActionQueueFileName svlircib # prefixnaam voor spoolfiles ( wissen )
$ActionQueueMaxDiskSpace 1g # max grote spoolfiles
$ActionQueueSaveOnShutdown on
$ActionQueueType LinkedList # asynchroon
$ActionResumeRetryCount -1 # blijven proberen if server down
$ActionSendStreamDriverAuthMode anon # Geen client-authenticatie

template(name=”JournalTemplate” type=”string” string=”%$!all-json%\n” ) #template for messages
action(type=”omfwd” protocol=”tcp” port=”6528” Target=”testserver” template=”JournalTemplate”)

Please let us know why in the second case queue is created when remote ELK server not reachable.

Источник

error writing pid file (creation stage) #3360

Comments

hxwang1024 commented Dec 19, 2018

/rsyslog]$ ./sbin/rsyslogd -f ./conf/rsyslog.conf -n -i ./run/rsyslog.pid
rsyslogd: error writing pid file (creation stage)
: Permission denied
rsyslogd: run failed with error -3000 (see rsyslog.h or try http://www.rsyslog.com/e/3000 to learn what that number means)

The text was updated successfully, but these errors were encountered:

rgerhards commented Dec 19, 2018

whxloveyrh commented Dec 27, 2018

[root@xxxxxx rsyslog]# ls
bin conf include lib lib64 log run sbin share var
[root@xxxxxx rsyslog]# ./sbin/rsyslogd -i ./run/syslogd.pid -f ./conf/rsyslog.conf -dn
Starting parse
Entering state 0
.
Cleanup: popping token $end ()
Cleanup: popping nterm conf ()
rsyslogd: error writing pid file (creation stage)
: No such file or directory
rsyslogd: run failed with error -3000 (see rsyslog.h or try http://www.rsyslog.com/e/3000 to learn what that number means)

whxloveyrh commented Dec 29, 2018

I use root account to launch rsyslog

rgerhards commented Dec 29, 2018

Note the strace .

rgerhards commented Dec 29, 2018

also do rsyslogd -v and post result.

lock bot commented Dec 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Footer

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Der Flounder

Fixing Homebrew’s rsyslog on macOS Catalina

As part of some recent testing, I needed to install rsyslog and the instructions I had referenced using Homebrew to do it. I used the following procedure to do it:

1. Set up a new VM running macOS 10.15.3 in VMware Fusion.

2. Inside the VM, open Terminal and install Homebrew by running the following command:

3. Once Homebrew was installed, install rsyslog by running the following command:

4. Copy a pre-configured rsyslog.conf file to /usr/local/etc/rsyslog.conf.

5. Set the following permissions on /usr/local/etc/rsyslog.conf:

6. Start rsyslog by running the following command with root privileges:

When I checked on rsyslog though, it wasn’t running or accepting logs from remote Macs like it should be. What had happened?

Update – 3-5-2020: The problem described by this post has now been fixed:

For more details, please see below the jump.

When I checked the system log, I saw a number of entries which looked like this:

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters

The rsyslogd process was starting and crashing almost immediately. To stop rsyslog from attempting to launch again, I ran the following commands with root privileges:

After that, I started investigating to figure out what had gone wrong.. Since the problem happened almost immediately after launch, I suspected a problem with how rsyslog was being launched. The LaunchD item which starts rsyslog is /usr/local/Cellar/rsyslog/8.2001.0/homebrew.mxcl.rsyslog.plist and it looks like this:

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters

From there, I was able to see the command that was being used to start rsyslog:

Next, I tried to run this command manually with root privileges:

When I did so, I got the following output:

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters

As part of some recent testing, I needed to install rsyslog and the instructions I had referenced using Homebrew to do it. I used the following procedure to do it:

1. Set up a new VM running macOS 10.15.3 in VMware Fusion.

2. Inside the VM, open Terminal and install Homebrew by running the following command:

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

3. Once Homebrew was installed, install rsyslog by running the following command:

brew install rsyslog

4. Copy a pre-configured rsyslog.conf file to /usr/local/etc/rsyslog.conf.

5. Set the following permissions on /usr/local/etc/rsyslog.conf:

File permissions

Owner: root - read, write
Group: wheel - read
Everyone: read

6. Start rsyslog by running the following command with root privileges:

brew services start rsyslog

When I checked on rsyslog though, it wasn’t running or accepting logs from remote Macs like it should be. What had happened?

Update – 3-5-2020: The problem described by this post has now been fixed:

For more details, please see below the jump.

When I checked the system log, I saw a number of entries which looked like this:

The rsyslogd process was starting and crashing almost immediately. To stop rsyslog from attempting to launch again, I ran the following commands with root privileges:

brew services stop rsyslog

After that, I started investigating to figure out what had gone wrong.. Since the problem happened almost immediately after launch, I suspected a problem with how rsyslog was being launched. The LaunchD item which starts rsyslog is /usr/local/Cellar/rsyslog/8.2001.0/homebrew.mxcl.rsyslog.plist and it looks like this:

From there, I was able to see the command that was being used to start rsyslog:

/usr/local/opt/rsyslog/sbin/rsyslogd -n -f /usr/local/etc/rsyslog.conf -i /usr/local/var/run/rsyslogd.pid

Next, I tried to run this command manually with root privileges:

/usr/local/opt/rsyslog/sbin/rsyslogd -n -f /usr/local/etc/rsyslog.conf -i /usr/local/var/run/rsyslogd.pid

When I did so, I got the following output:

When I checked on /usr/local/var/run, I discovered that the /usr/local/var/run directory didn’t exist. Since it didn’t exist, rsyslogd couldn’t write the following file to it:

/usr/local/var/run/rsyslogd.pid

To fix this, I ran the following command to create the directory:

mkdir -p /usr/local/var/run

Once the /usr/local/var/run directory existed, I ran the following command with root privileges:

brew services start rsyslog

This time, rsyslog started without a problem and I was able to continue with my testing.

I am trying to verify that a cronjob ran on WSL2. Sources have told me to check /var/log/syslog. When I navigated there, syslog did not exist. Sources then told me to run service rsyslog start to start the service. When I do so, I get this error message:

deverteuils@:~$ service rsyslog start
 * Starting enhanced syslogd rsyslogd                                                                                mknod: /dev/xconsole: Permission denied
chown: cannot access '/dev/xconsole': No such file or directory
rsyslogd: error writing pid file (creation stage)
: Permission denied
rsyslogd: run failed with error -3000 (see rsyslog.h or try https://www.rsyslog.com/e/3000 to learn what that number means)
rsyslog startup failure: error reading "fork pipe": No such file or directory
                                                                                                              [ OK ]

I then made the change mentioned here to my etc/init.d/rsyslog file. However it did not do the trick:

deverteuils@:/etc/init.d$ service rsyslog start
 * Starting enhanced syslogd rsyslogd                                                                                rsyslogd: error writing pid file (creation stage)
: Permission denied
rsyslogd: run failed with error -3000 (see rsyslog.h or try https://www.rsyslog.com/e/3000 to learn what that number means)
rsyslog startup failure: error reading "fork pipe": No such file or directory
                                                                                                              [ OK ]

I also tried making the change mentioned here to no avail.

My next thought is to just install xconsole, but I’m not having luck with that either and at this point I’ve spent a lot of time on the issue.

My question is: how can I start up rsyslog without using xconsole and/or download xconsole to my machine?

For reference

deverteuils@:~$ lsb_release -d
Description:    Ubuntu 20.04.5 LTS

deverteuils@:/etc/init.d$ cat rsyslog
#! /bin/sh
### BEGIN INIT INFO
# Provides:          rsyslog
# Required-Start:    $remote_fs $time
# Required-Stop:     umountnfs $time
# X-Stop-After:      sendsigs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: enhanced syslogd
# Description:       Rsyslog is an enhanced multi-threaded syslogd.
#                    It is quite compatible to stock sysklogd and can be
#                    used as a drop-in replacement.
### END INIT INFO

#
# Author: Michael Biebl <biebl@debian.org>
#

# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="enhanced syslogd"
NAME=rsyslog

RSYSLOGD=rsyslogd
DAEMON=/usr/sbin/rsyslogd
PIDFILE=/run/rsyslogd.pid

SCRIPTNAME=/etc/init.d/$NAME

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] && . /etc/default/$NAME

# Define LSB log_* functions.
. /lib/lsb/init-functions

do_start()
{
        # Return
        #   0 if daemon has been started
        #   1 if daemon was already running
        #   other if daemon could not be started or a failure occured
        start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- $RSYSLOGD_OPTIONS
}

do_stop()
{
        # Return
        #   0 if daemon has been stopped
        #   1 if daemon was already stopped
        #   other if daemon could not be stopped or a failure occurred
        start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --exec $DAEMON
}

#
# Tell rsyslogd to close all open files
#
do_rotate() {
        start-stop-daemon --stop --signal HUP --quiet --pidfile $PIDFILE --exec $DAEMON
}

create_xconsole() {
        XCONSOLE=/dev/xconsole
        if [ "$(uname -s)" != "Linux" ]; then
                XCONSOLE=/run/xconsole
                ln -sf $XCONSOLE /dev/xconsole
        fi
        if [ ! -e $XCONSOLE ]; then
                mknod -m 640 $XCONSOLE p
                chown root:adm $XCONSOLE
                [ -x /sbin/restorecon ] && /sbin/restorecon $XCONSOLE
        fi
}

sendsigs_omit() {
        OMITDIR=/run/sendsigs.omit.d
        mkdir -p $OMITDIR
        ln -sf $PIDFILE $OMITDIR/rsyslog
}

case "$1" in
  start)
        log_daemon_msg "Starting $DESC" "$RSYSLOGD"
        #create_xconsole
        do_start
        case "$?" in
                0) sendsigs_omit
                   log_end_msg 0 ;;
                1) log_progress_msg "already started"
                   log_end_msg 0 ;;
                *) log_end_msg 1 ;;
        esac

        ;;
  stop)
        log_daemon_msg "Stopping $DESC" "$RSYSLOGD"
        do_stop
        case "$?" in
                0) log_end_msg 0 ;;
                1) log_progress_msg "already stopped"
                   log_end_msg 0 ;;
                *) log_end_msg 1 ;;
        esac

        ;;
  rotate)
        log_daemon_msg "Closing open files" "$RSYSLOGD"
        do_rotate
        log_end_msg $?
        ;;
  restart|force-reload)
        $0 stop
        $0 start
        ;;
  try-restart)
        $0 status >/dev/null 2>&1 && $0 restart
        ;;
  status)
        status_of_proc -p $PIDFILE $DAEMON $RSYSLOGD && exit 0 || exit $?
        ;;
  *)
        echo "Usage: $SCRIPTNAME {start|stop|rotate|restart|force-reload|try-restart|status}" >&2
        exit 3
        ;;
esac

:

I was trying to configure rsyslog to forward logs from a specific file to a syslogserver and I ended up purging the whole configuration (the rsyslog service was stuck — wouldn’t start) ..

so I purged everything, and installed everything from scratch again … and now it fails when I try to start it.

here is the OS version:

~# cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

here is the rsyslog version

~# rsyslogd -v
rsyslogd  8.2212.0 (aka 2022.12) compiled with:
    PLATFORM:               x86_64-pc-linux-gnu
    PLATFORM (lsb_release -d):      
    FEATURE_REGEXP:             Yes
    GSSAPI Kerberos 5 support:      No
    FEATURE_DEBUG (debug build, slow code): No
    32bit Atomic operations supported:  Yes
    64bit Atomic operations supported:  Yes
    memory allocator:           system default
    Runtime Instrumentation (slow code):    No
    uuid support:               Yes
    systemd support:            No
    Config file:                /etc/rsyslog.conf
    PID file:               /var/run/rsyslogd.pid
    Number of Bits in RainerScript integers: 64

See https://www.rsyslog.com for more information.

Here is my rsyslog.conf

~# cat /etc/rsyslog.conf 
#  /etc/rsyslog.conf    Configuration file for rsyslog.
#
#           For more information see
#           /usr/share/doc/rsyslog-doc/html/rsyslog_conf.html


#################
#### MODULES ####
#################

module(load="imuxsock") # provides support for local system logging
module(load="imklog")   # provides kernel logging support
#module(load="immark")  # provides --MARK-- message capability

# provides UDP syslog reception
#module(load="imudp")
#input(type="imudp" port="514")

# provides TCP syslog reception
#module(load="imtcp")
#input(type="imtcp" port="514")


###########################
#### GLOBAL DIRECTIVES ####
###########################

#
# Use traditional timestamp format.
# To enable high precision timestamps, comment out the following line.
#
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat

#
# Set the default permissions for all log files.
#
$FileOwner root
$FileGroup adm
$FileCreateMode 0640
$DirCreateMode 0755
$Umask 0022

#
# Where to place spool and state files
#
$WorkDirectory /var/spool/rsyslog

#
# Include all config files in /etc/rsyslog.d/
#
$IncludeConfig /etc/rsyslog.d/*.conf


###############
#### RULES ####
###############

#
# First some standard log files.  Log by facility.
#
auth,authpriv.*         /var/log/auth.log
*.*;auth,authpriv.none      -/var/log/syslog
#cron.*             /var/log/cron.log
daemon.*            -/var/log/daemon.log
kern.*              -/var/log/kern.log
lpr.*               -/var/log/lpr.log
mail.*              -/var/log/mail.log
user.*              -/var/log/user.log

#
# Logging for the mail system.  Split it up so that
# it is easy to write scripts to parse these files.
#
mail.info           -/var/log/mail.info
mail.warn           -/var/log/mail.warn
mail.err            /var/log/mail.err

#
# Some "catch-all" log files.
#
*.=debug;
    auth,authpriv.none;
    news.none;mail.none -/var/log/debug
*.=info;*.=notice;*.=warn;
    auth,authpriv.none;
    cron,daemon.none;
    mail,news.none      -/var/log/messages

#
# Emergencies are sent to everybody logged in.
#
*.emerg             :omusrmsg:*

and lastly the systemd service (which is a soft link to /lib/systemd/system/rsyslog.service)

~# cat /etc/systemd/system/syslog.service 
[Unit]
Description=System Logging Service
Requires=syslog.socket
Documentation=man:rsyslogd(8)
Documentation=man:rsyslog.conf(5)
Documentation=https://www.rsyslog.com/doc/

[Service]
Type=notify
ExecStart=/usr/sbin/rsyslogd -n 
StandardOutput=null
Restart=on-failure

# Increase the default a bit in order to allow many simultaneous
# files to be monitored, we might need a lot of fds.
#LimitNOFILE=16384

[Install]
WantedBy=multi-user.target
Alias=syslog.service

when I run /usr/sbin/rsyslogd -n I am getting

~# /usr/sbin/rsyslogd -n
rsyslogd: pidfile '/var/run/rsyslogd.pid' and pid 6260 already exist.
If you want to run multiple instances of rsyslog, you need to specify
different pid files for them (-i option).
rsyslogd: run failed with error -3000 (see rsyslog.h or try https://www.rsyslog.com/e/3000 to learn what that number means)

service status says:

~# systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2022-12-22 08:05:56 CET; 8s ago
     Docs: man:rsyslogd(8)
           man:rsyslog.conf(5)
           https://www.rsyslog.com/doc/
  Process: 6464 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE)
 Main PID: 6464 (code=exited, status=1/FAILURE)

Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: rsyslog.service: Main process exited, code=exited, status=1/FAILURE
Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: rsyslog.service: Failed with result 'exit-code'.
Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: Failed to start System Logging Service.
Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: rsyslog.service: Service RestartSec=100ms expired, scheduling restart.
Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 5.
Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: Stopped System Logging Service.
Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: rsyslog.service: Start request repeated too quickly.
Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: rsyslog.service: Failed with result 'exit-code'.
Dec 22 08:05:56 TW-3CXNFA-B systemd[1]: Failed to start System Logging Service.

I am a bit stuck here … I googled the «pid already exist» message and many others but it led me nowhere

I would appreciate a bit of nudge here please Any ideas what I need to do?

———— EDIT ————

I tried this according to the tips from you guys …

edited (r)syslog.service and add -iNONE as a param

~# cat /etc/systemd/system/syslog.service 
[Unit]
Description=System Logging Service
Requires=syslog.socket
Documentation=man:rsyslogd(8)
Documentation=man:rsyslog.conf(5)
Documentation=https://www.rsyslog.com/doc/

[Service]
Type=notify
ExecStart=/usr/sbin/rsyslogd -n -iNONE
StandardOutput=null
Restart=on-failure

#Increase the default a bit in order to allow many simultaneous
#files to be monitored, we might need a lot of fds.
#LimitNOFILE=16384

[Install]
WantedBy=multi-user.target
Alias=syslog.service

reloaded the daemon -> systemctl daemon-reload (no error messages)

stopped both systemctl stop syslog.socket rsyslog.service

checked the status of both

~# systemctl status syslog.socket rsyslog.service
● syslog.socket - Syslog Socket
   Loaded: loaded (/lib/systemd/system/syslog.socket; static; vendor preset: disabled)
   Active: inactive (dead) since Thu 2022-12-22 14:57:32 CET; 18s ago
     Docs: man:systemd.special(7)
           https://www.freedesktop.org/wiki/Software/systemd/syslog
   Listen: /run/systemd/journal/syslog (Datagram)

Dec 22 10:17:58 TW-3CXNFA-B systemd[1]: Listening on Syslog Socket.
Dec 22 14:57:32 TW-3CXNFA-B systemd[1]: syslog.socket: Succeeded.
Dec 22 14:57:32 TW-3CXNFA-B systemd[1]: Closed Syslog Socket.

● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Thu 2022-12-22 14:57:32 CET; 18s ago
     Docs: man:rsyslogd(8)
           man:rsyslog.conf(5)
           https://www.rsyslog.com/doc/
  Process: 22681 ExecStart=/usr/sbin/rsyslogd -n -iNONE (code=exited, status=0/SUCCESS)
 Main PID: 22681 (code=exited, status=0/SUCCESS)

Dec 22 14:56:59 TW-3CXNFA-B systemd[1]: Starting System Logging Service...
Dec 22 14:57:32 TW-3CXNFA-B systemd[1]: rsyslog.service: Succeeded.
Dec 22 14:57:32 TW-3CXNFA-B systemd[1]: Stopped System Logging Service.

both are inactive .. I then checked if there is any active PID (all good)

~# ps axu | grep rsyslog
root     22747  0.0  0.0   6072   888 pts/0    S+   14:59   0:00 grep rsyslog

verified if there is the pid file ls /var/run/ | grep syslog (none)

I then started the service which resulted in the timeout message

~# systemctl start rsyslog
Job for rsyslog.service failed because a timeout was exceeded.
See "systemctl status rsyslog.service" and "journalctl -xe" for details.

checking the status

~# systemctl status rsyslog.service
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: activating (start) since Thu 2022-12-22 15:03:16 CET; 1min 26s ago
     Docs: man:rsyslogd(8)
           man:rsyslog.conf(5)
           https://www.rsyslog.com/doc/
 Main PID: 22896 (rsyslogd)
    Tasks: 4 (limit: 1136)
   Memory: 824.0K
   CGroup: /system.slice/rsyslog.service
           └─22896 /usr/sbin/rsyslogd -n -iNONE

Dec 22 15:03:16 TW-3CXNFA-B systemd[1]: Starting System Logging Service...

plus journal:

~# journalctl -xe
-- A stop job for unit rsyslog.service has finished.
-- 
-- The job identifier is 25478 and the job result is done.
Dec 22 15:03:16 TW-3CXNFA-B systemd[1]: Starting System Logging Service...
-- Subject: A start job for unit rsyslog.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit rsyslog.service has begun execution.
-- 
-- The job identifier is 25478.
Dec 22 15:04:46 TW-3CXNFA-B systemd[1]: rsyslog.service: Start operation timed out. Terminating.
Dec 22 15:04:46 TW-3CXNFA-B systemd[1]: rsyslog.service: Failed with result 'timeout'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit rsyslog.service has entered the 'failed' state with result 'timeout'.
Dec 22 15:04:46 TW-3CXNFA-B systemd[1]: Failed to start System Logging Service.
-- Subject: A start job for unit rsyslog.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit rsyslog.service has finished with a failure.
-- 
-- The job identifier is 25478 and the job result is failed.
Dec 22 15:04:46 TW-3CXNFA-B systemd[1]: rsyslog.service: Service RestartSec=100ms expired, scheduling restart.
Dec 22 15:04:46 TW-3CXNFA-B systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 2.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Automatic restarting of the unit rsyslog.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 22 15:04:46 TW-3CXNFA-B systemd[1]: Stopped System Logging Service.
-- Subject: A stop job for unit rsyslog.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit rsyslog.service has finished.
-- 
-- The job identifier is 25554 and the job result is done.
Dec 22 15:04:46 TW-3CXNFA-B systemd[1]: Starting System Logging Service...
-- Subject: A start job for unit rsyslog.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit rsyslog.service has begun execution.
-- 
-- The job identifier is 25554.
Dec 22 15:05:01 TW-3CXNFA-B CRON[22955]: pam_unix(cron:session): session opened for user root by (uid=0)
Dec 22 15:05:01 TW-3CXNFA-B CRON[22956]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec 22 15:05:01 TW-3CXNFA-B CRON[22955]: pam_unix(cron:session): session closed for user root

wth am I missing?