Failed to open the log file

Добрый вечер.
у меня при вводе команды вылезает следующая ошибка.

Я так понимаю, что у Сфинкса нет прав на запись.
Какие права нужно установить на папки

log = /var/log/sphinxsearch/searchd.log
query_log = /var/log/sphinxsearch/query.log
p > binlog_path = /var/lib/sphinxsearch/data/
path = /var/lib/sphinxsearch/data/bitrix

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

  • Вопрос задан более года назад
  • 743 просмотра

ps auxwwww | grep sphinxsearch
Проверила , кто, это моя учетная запись.
Вопрос такой, именно
сменить владельца root на конкретные папки
на /var/log/sphinxsearch/,/var/lib/sphinxsearch/, /var/run/sphinxsearch/,
то есть на те папки, в которых участвует сфинкс.

И почему root сам не может запускать sphinxsearch?

моя учетка my
я не знаю как правильно, сделала

вроде заработало
я писала вместо

Не знаю верно ли, так как
ps auxwwww | grep sphinxsearch
это я . Как вы думаете?

правда у меня вылезли

Адрес сайта it.loc:81, размещен локально

RabIN, FATAL: failed to open log file ‘/var/log/sphinxsearc
на эту папку проверьте доступ, сфинкс туда не смог достучаться. Если не получается — ставьте максимальные права, затем лишние пробуйте убирать. Проблема явно в уровне доступа, соответственно только изменением прав бороться. В принципе в лог папку можно дать полный доступ для всех пользователей, это не критично.

И поставьте себе mc, все же проще через оболочку все это делать чем с голой консоли.

I’m usin dnschef in my Linux machine, but it gave me this error.

How to fix this issue?

Plus, I can use dnschef (which will use localhost network card lo by default) and it doesn’t have such issue.

1 Answer 1

Take a look at this tutorial. It shows you the various ways you can use dnschef .

DNSChef is capable of storing activity log in an external file using the —logfile log1.txt command line parameter. Below is a snippet of a sample DNSChef session:

So something like this:

The full usage

Issue #10 — cannot open logfile

Your issue looks like it’s actually a false positive though. The real error is this:

IOError code 13 (permission denied) is thrown on an attempt to bind to the default port 53 which requires the root permissions

I found that here in the upstream repo for dnschef —

In the comments people are stating that this issue is still not resolved, and even when running dnschef as root, it’s still reporting the error.

Its all about Database

Search This Blog

Unable to open the log file (mysqld)

While starting the server you may find the below errors sometimes, it’s because of unintentionally deleting the MySQL Binary Log files. When starting mysql if the server unable to find the mysql-bin-log files then below errors will arise.

Do we have a solution to get rid of this and start MySQL again?

Well, we have two types of workarounds to start MySQL again.

1. Deleting the missed files in binlog .index file
2. Disabling the binlog logging on my.cnf file

1. Deleting the missed files in binlog .index file

Delete the mysql-bin.000023 from the above file and restart the mysqld.

2. Disabling the binlog logging on my.cnf file

In this step, open my.cnf and set the value of set_log_bin to 0 and purge all the existing binary logs

Save the above file and restart the mysql service. Once after login to the server purge the bin logs.

This will delete the existing logs from the server.
After this step, Enable the Binary log again to write the changes to binlog files.

To do that login to MySQL again and do below.

Once after finishing this, edit the my.cnf file and set the sql_log_bin from 0 to 1and restart the service.

Note: The second procedure is not the recommended way to apply in Production.

  • Get link
  • Facebook
  • Twitter
  • Pinterest
  • Email
  • Other Apps


  • Get link
  • Facebook
  • Twitter
  • Pinterest
  • Email
  • Other Apps


Post a Comment

Popular posts from this blog

Installing,Starting,Stopping PostgreSQL Server on Linux OS

In this post, we will see how to Install and Run PostgreSQL on Linux machines.

There are three ways to installation procedures to download the software.

1. Binary Installation
2. Yum Installation
3. RPM Installation

In this post, will see how to install PostgreSQL using Binary installation.

1. Download the binaries from the official website.
$ wget 2. Untar the downloaded binaries.
$ tar -xvzf postgresql-9.6.2-4-linux-x64-binaries.tar.gz 3. Create appropriate data directories and permissions with root user to run PostgreSQL Server.
# mkdir -p /var/lib/pgsql/data # chown -R psql /var/lib/pgsql/data # su psql 4. Now change the directory path to the downloaded software path
$ cd /home/psql/softwares/pgsql 5. Initialize the data directories required for PostgreSQL to run, there are two ways to initialize the directories.
$ initdb -D /usr/local/pgsql/data Alternatively, we can also initialize using pg_ctl

  • Get link
  • Facebook
  • Twitter
  • Pinterest
  • Email
  • Other Apps

Monitoring MySQL with Percona Monitoring and Management

In this blog post we will see how to monitor MySQL databases using the open source monitoring tool provided by Percona, referred as Percona Monitoring and Management (PMM).

About PMM: Percona Monitoring and Management (PMM) is an open-source platform for managing and monitoring MySQL and MongoDB performance. It is developed by Percona in collaboration with experts in the field of managed database services, support and consulting.
PMM is a free and open-source solution that you can run in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL and MongoDB servers to ensure that your data works as efficiently as possible. Basic Requirements: 1. Need at least one Linux server to install PMM Client and PMM Server. 2. Need Operating System — root user credentials 3. Default port’s(80) have to be open if using to or more servers. 4. A MySQL user is required to capture the Queries in the Database. 5. A Docker service has to be installed…

[an error occurred while processing the directive]
Карта сайта