ERPNext down ver 10.42

ERPNext
1

Traceback (most recent call last):
File “/usr/local/bin/bench”, line 11, in
load_entry_point(‘bench’, ‘console_scripts’, ‘bench’)()
File “/home/frappe/.bench/bench/cli.py”, line 40, in cli
bench_command()
File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 722, in call

File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 697, in main

File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 1063, in invoke

File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 895, in invoke

File “/usr/local/lib/python2.7/dist-packages/click/core.py”, line 535, in invoke

File “/home/frappe/.bench/bench/commands/init.py”, line 31, in bench_command
setup_logging(bench_path=bench_path)
File “/home/frappe/.bench/bench/utils.py”, line 299, in setup_logging
hdlr = logging.FileHandler(log_file)
File “/usr/lib/python2.7/logging/init.py”, line 913, in init

File “/usr/lib/python2.7/logging/init.py”, line 943, in _open

IOError: [Errno 30] Read-only file system: '/home/frappe/frappe-bench/logs/bench.lo

2

Hi @amit_vaid,

read-only file system indicates an issue with your system. The file system can get into this state for several reasons.

Short-term: a reboot often recovers the file system. That should get your system back to work.

However, you have to look for the root cause for the read-only file system, such as hardware failure, …