loongson & MySQL 如何处理 /etc/lsb-base-logging.sh: line 72: RUNLEVEL: unbound variable

最新推荐文章于 2025-06-03 16:47:57 发布

转载最新推荐文章于 2025-06-03 16:47:57 发布 · 1k 阅读

文章标签：

#mysql #initialization #debian #file #ubuntu #action

python技术同时被 2 个专栏收录

9 篇文章

订阅专栏

plone技术

5 篇文章

订阅专栏

本文介绍了一种在龙芯电脑上安装MySQL过程中遇到的RUNLEVEL变量未定义的问题及其解决方案。通过手动初始化RUNLEVEL变量，解决了安装过程中出现的错误。

在龙芯电脑上安装mysql的时候, 出现错误, 而且使用了编译源码方式也没能成功.

后在网上查到,原来是启动脚本里面的变量没定义而造成的.

&&&&&&&&&&&&提示如下&&&&&&&&&&&&

解压缩后会消耗掉 0B 的额外空间。
正在设置 mysql-server-5.0 (5.0.51a-24) ...
/etc/lsb-base-logging.sh: line 72: RUNLEVEL: unbound variable
invoke-rc.d: init script mysql, action "stop" failed.
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

I had this problem today, I don't believe it's mysql related, and there was no need to do anything with mysql to work around it.

I encountered this today on dist-upgrade of debian sid, in sidux [ http://sidux.com ] run sid.

apt-get install -f did not resolve it, dist-upgrade halted on errors no matter what I did.

The same exact error, so after poking around a little, and realizing that maybe the error message actually meant what it said, that the RUNLEVEL variable on line 42 was in fact not set.

Because I needed the upgrade to finish, I just did a simple hack, like this:

#

# The first piece is just what it is /lib/lsb/init-functions

# for debian. We probably should supply something else for

# ubuntu.

#

# TODO we need to know whats the next step in the progress

# file and send exit to Splashy before X starts (after setting

# the percentage to the right amount)

#### NOTE: I ADDED THIS RUNLEVEL VARIABLE INITIALIZATION HERE:

RUNLEVEL=''

# int log_end_message (int exitstatus)

log_end_msg () {

# If no arguments were passed, return

[ -z "${1:-}" ] && return 1

Adding that RUNLEVEL initiatialization fixed the halt, allowed mysql to finish installing. I want to stress though, this looks like an error in this config file by the, I assume, ubuntu, developer.

I'm not sure what the consequences to this hack are, but since I don't use splashy it's probably not going to be that bad.

Sorry about the extra junk that's a bug with this blog software, not my fault.