Не запускается Bareos-dir

0

1

Вылетел диск из рейда, рейд пересоздал успешно, но тут случился косяк с Bareos.

root@root:/var/lib/bareos# /etc/init.d/bareos-dir start

[....] Starting bareos-dir (via systemctl): bareos-dir.serviceJob for bareos-director.service failed because of unavailable resources or another system error.
See "systemctl status bareos-director.service" and "journalctl -xe" for details.
 failed!

Вывод journalctl -xe

фев 13 09:43:19 root systemd[1]: Starting Bareos Director Daemon service...
-- Subject: Начинается запуск юнита bareos-director.service
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Начат процесс запуска юнита bareos-director.service.
фев 13 09:43:19 root bareos-dir[4275]: [48B blob data]
фев 13 09:43:19 root bareos-dir[4275]: Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
фев 13 09:43:19 root bareos-dir[4278]: [48B blob data]
фев 13 09:43:19 root bareos-dir[4278]: Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
фев 13 09:43:19 root systemd[1]: bareos-director.service: PID file /var/lib/bareos/bareos-dir.9101.pid not readable
фев 13 09:43:19 root systemd[1]: Failed to start Bareos Director Daemon service.
-- Subject: Ошибка юнита bareos-director.service
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Произошел сбой юнита bareos-director.service.
--
-- Результат: failed.
фев 13 09:43:19 root systemd[1]: bareos-director.service: Unit entered failed state.
фев 13 09:43:19 root systemd[1]: bareos-director.service: Failed with result 'resources'.

При этом действительно файла /var/lib/bareos/bareos-dir.9101.pid нету. Пробывал пустой создавать не чего не помогло.

Пробывал apt-get --reinstall install bareos Тоже не помогло.

Куда копать? Спасибо заранее.

Ссылка

←	Однострочный конфиг по типу json'a

Быстрый и безопасный мониторинг JVM-приложений с помощью магии BPF

→

Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU фев 13 09:43:19 root bareos-dir[4278]: [48B blob data] фев 13 09:43:19 root bareos-dir[4278]: Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

Ошибка в конфигурационном файле, видимо, некорректный конец строки.

Используй тег [code][/code], кнопку «Предпросмотр» и изучи ссылку, которая указана в форме помещения сообщения на форум между текстовым полем и кнопками.

Удачи.

kostik87 ★★★★★
(13.02.18 09:47:56 MSK)

Ответ на: комментарий от kostik87 13.02.18 09:47:56 MSK

А как узнать какой конфиг не верный?

root@SL06002508001:/var/lib/bareos# bareos-dir -t -d100

bareos-dir (10): dird.c:245-0 Debug level = 100
bareos-dir (100): parse_conf.c:151-0 config file = /etc/bareos/bareos-dir.d/*/*.conf
bareos-dir (100): lex.c:333-0 glob /etc/bareos/bareos-dir.d/*/*.conf: 32 files
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/catalog/MyCatalog.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/client/bareos-fd.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/console/admin.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/console/bareos-mon.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/director/bareos-dir.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/fileset/Catalog-1s_12.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/fileset/Catalog.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/fileset/Catalog-serv-doc_253.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/fileset/LinuxAll.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/fileset/SelfTest.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/fileset/Windows All Drives.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/job/Backup_1s.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/job/Backup_253.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/job/backup-bareos-fd.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/job/BackupCatalog.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/jobdefs/DefaultJob.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/jobdefs/Job_1s.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/jobdefs/Job_253.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/job/RestoreFiles.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/messages/Daemon.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/messages/Standard.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/pool/Differential.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/pool/Full_1s.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/pool/Full_253.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/pool/Full.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/pool/Incremental.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/pool/Scratch.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/profile/operator.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/profile/webui-admin.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/schedule/WeeklyCycleAfterBackup.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/schedule/WeeklyCycle.conf
bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/storage/File.conf
bareos-dir (10): lex.c:980-0 ERROR TERMINATION: Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUu
]▒w>Vbareos-dir: ERROR TERMINATION at lex.c:980
Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUu

kiril14
(13.02.18 10:04:11 MSK) автор топика

Ответ на: комментарий от kiril14 13.02.18 10:04:11 MSK

Видимо, вот он:

bareos-dir (100): lex.c:227-0 open config file: /etc/bareos/bareos-dir.d/storage/File.conf

неверный.

kostik87 ★★★★★
(13.02.18 10:11:45 MSK)

Ответ на: комментарий от kostik87 13.02.18 10:11:45 MSK

root@SL06002508001:/var/lib/bareos# cat /etc/bareos/bareos-dir.d/storage/File.conf

Storage {
  Name = File
  Address = test                # N.B. Use a fully qualified name here (do not use "localhost" here).
  Password = "********************"
  Device = FileStorage
  Media Type = File
}

Может быть когда у меня упал рейд у меня пароль изменился или потерялся. В целях безопасности поменял на ******. Как его генерировать заново? Не могу в man найти.

kiril14
(13.02.18 10:37:40 MSK) автор топика

Ответ на: комментарий от kiril14 13.02.18 10:37:40 MSK

Тут указано не на то, что пароль неправильный, а на то, что перевод строки некорректный, у тебя где-то стоит перевод UNIX, а где-то DOS, а пароль, вроде как, просто в открытом виде пишется.

kostik87 ★★★★★
(13.02.18 10:46:00 MSK)
Последнее исправление: kostik87 13.02.18 10:46:23 MSK (всего исправлений: 1)

Ответ на: комментарий от kostik87 13.02.18 10:46:00 MSK

Заново через nano набрал все что было внутри, ситуация аналогичная.

kiril14
(13.02.18 11:16:57 MSK) автор топика

Ответ на: комментарий от kiril14 13.02.18 11:16:57 MSK

Посмотри vim, разные переводы строки будут выглядеть вот так:

echo -e "\n\r\n\r"  >> /tmp/123
vim /tmp/123


^M
^M
~

ну и возможно, что проблема в предыдущем конфигурационном файле.

kostik87 ★★★★★
(13.02.18 11:19:18 MSK)

почему это в Development? типичная админская заморочка

Iron_Bug ★★★★★
(13.02.18 11:51:24 MSK)

Ссылка

Ответ на: комментарий от kostik87 13.02.18 11:19:18 MSK

В vim переводы строк нормальные. Нельзя ли узнать на какой именно ругается bareos?

kiril14
(13.02.18 11:54:46 MSK) автор топика

Ответ на: комментарий от kiril14 13.02.18 11:54:46 MSK

Не могу найти я эти пробелы, и что еще страшнее нашел еще одну ошибку в syslog:

Feb 13 14:47:21 SL06002508001 systemd[1]: Starting Bareos Director Daemon service...
Feb 13 14:47:21 SL06002508001 bareos-dir[8921]: #020▒c(▒Ubareos-dir: ERROR TERMINATION at parse_conf.c:198
Feb 13 14:47:21 SL06002508001 bareos-dir[8921]: Config error: Cannot open config file "/etc/bareos/bareos-dir.d/*/*.conf": Отказано в доступе

kiril14
(13.02.18 15:08:08 MSK) автор топика

Ответ на: комментарий от kiril14 13.02.18 15:08:08 MSK

В bacula-dir был ключ -d , он выдавал отладочный лог при старте.

~~Bobby_~~
(13.02.18 15:12:40 MSK)

Ответ на: комментарий от Bobby_ 13.02.18 15:12:40 MSK

bareos-dir -d10

bareos-dir (10): lex.c:980-0 ERROR TERMINATION: Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
-C(Vbareos-dir: ERROR TERMINATION at lex.c:980
Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

kiril14
(13.02.18 15:16:03 MSK) автор топика

Ответ на: комментарий от kiril14 13.02.18 15:16:03 MSK

Увеличь число в -d, в логе должно появиться название файла конфига, номер строки и колонки типа:

Config error: expected a string, got T_EOL: = : line 236, col 12 of file /etc/bacula/bacula-dir.conf

~~Bobby_~~
(13.02.18 15:52:28 MSK)

Ссылка

Ответ на: комментарий от kiril14 13.02.18 15:16:03 MSK

Как вариант, попробуй запустить с конфигом по умолчанию, если запустится, аккуратно его редактируй, добавляя свои опции.

~~Bobby_~~
(13.02.18 15:54:13 MSK)

Ответ на: комментарий от Bobby_ 13.02.18 15:54:13 MSK

Увеличил -d:

bareos-dir (10): lex.c:980-0 ERROR TERMINATION: Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
bareos-dir (850): message.c:858-0 Enter dispatch_message type=11 msg=bareos-dir: ERROR TERMINATION at lex.c:980
Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
▒^▒▒Ubareos-dir: ERROR TERMINATION at lex.c:980
Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
bareos-dir (850): message.c:1138-0 STDOUT for following msg: bareos-dir: ERROR TERMINATION at lex.c:980
Config error: expected a string, got T_EOL: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU

kiril14
(13.02.18 16:15:06 MSK) автор топика

Ответ на: комментарий от kiril14 13.02.18 16:15:06 MSK

Начни с дефолтного конфига и если запустится сделай diff со своим.

~~Bobby_~~
(13.02.18 16:19:50 MSK)

Ссылка

Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.

←	Однострочный конфиг по типу json'a

Development

Быстрый и безопасный мониторинг JVM-приложений с помощью магии BPF

→

Похожие темы