[opensuse] zypper dup : updatedb gets stuck
a week ago , upon completion of doing my weekly "zypper dup" , running "updatedb" got stuck and continued running `forever` - same today : "updatedb" got stuck ....... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/11/2018 22.31, ellanios82 wrote:
a week ago , upon completion of doing my weekly "zypper dup" , running "updatedb" got stuck and continued running `forever`
- same today : "updatedb" got stuck
Is that tumbleweed? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 03/11/2018 23:43, Carlos E. R. wrote:
On 03/11/2018 22.31, ellanios82 wrote:
a week ago , upon completion of doing my weekly "zypper dup" , running "updatedb" got stuck and continued running `forever`
- same today : "updatedb" got stuck Is that tumbleweed?
- Yes : that is TW .......... rgds -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82:
On 03/11/2018 23:43, Carlos E. R. wrote:
On 03/11/2018 22.31, ellanios82 wrote:
a week ago , upon completion of doing my weekly "zypper dup" , running "updatedb" got stuck and continued running `forever`
- same today : "updatedb" got stuck
Is that tumbleweed?
- Yes : that is TW
..........
rgds Could you provide some more info? Running TW here, no issues running updatedb.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/11/2018 23.03, Knurpht-openSUSE wrote:
Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82:
On 03/11/2018 23:43, Carlos E. R. wrote:
On 03/11/2018 22.31, ellanios82 wrote:
a week ago , upon completion of doing my weekly "zypper dup" , running "updatedb" got stuck and continued running `forever`
- same today : "updatedb" got stuck
Is that tumbleweed?
- Yes : that is TW
..........
rgds Could you provide some more info? Running TW here, no issues running updatedb.
For instance, paste the output of "df -h". Then, kill the process and run it on a terminal. "su - nobody" then run it. See if there are messages. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 04/11/2018 00:10, Carlos E. R. wrote: > On 03/11/2018 23.03, Knurpht-openSUSE wrote: >> Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82: >>> On 03/11/2018 23:43, Carlos E. R. wrote: >>>> On 03/11/2018 22.31, ellanios82 wrote: >>>>> a week ago , upon completion of doing my weekly "zypper dup" , running >>>>> "updatedb" got stuck and continued running `forever` >>>>> >>>>> >>>>> - same today : "updatedb" got stuck >>>> Is that tumbleweed? >>> - Yes : that is TW >>> >>> >>> .......... >>> >>> rgds >> Could you provide some more info? >> Running TW here, no issues running updatedb. > For instance, paste the output of "df -h". > > Then, kill the process and run it on a terminal. "su - nobody" then run > it. See if there are messages. - run in init 3 state : impossible to kill updatedb ......... rgds > -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* ellanios82 <ellanios82@gmail.com> [11-03-18 18:56]: > On 04/11/2018 00:10, Carlos E. R. wrote: > > On 03/11/2018 23.03, Knurpht-openSUSE wrote: > > > Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82: > > > > On 03/11/2018 23:43, Carlos E. R. wrote: > > > > > On 03/11/2018 22.31, ellanios82 wrote: > > > > > > a week ago , upon completion of doing my weekly "zypper dup" , running > > > > > > "updatedb" got stuck and continued running `forever` > > > > > > - same today : "updatedb" got stuck > > > > > Is that tumbleweed? > > > > - Yes : that is TW > > > > > > > > > > > > .......... > > > > > > > > rgds > > > Could you provide some more info? > > > Running TW here, no issues running updatedb. > > For instance, paste the output of "df -h". > > > > Then, kill the process and run it on a terminal. "su - nobody" then run > > it. See if there are messages. > > > - run in init 3 state : impossible to kill updatedb google for it, "opensuse updatedb" I had same problem, was iirc apparmor, yes: https://bugzilla.opensuse.org/show_bug.cgi?id=1089594 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/11/2018 01:40, Patrick Shanahan wrote:
- run in init 3 state : impossible to kill updatedb google for it, "opensuse updatedb" I had same problem, was iirc apparmor, yes: https://bugzilla.opensuse.org/show_bug.cgi?id=1089594
: aha : thanks ....... rgds -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/11/2018 23.53, ellanios82 wrote:
On 04/11/2018 00:10, Carlos E. R. wrote:
On 03/11/2018 23.03, Knurpht-openSUSE wrote:
Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82:
On 03/11/2018 23:43, Carlos E. R. wrote:
On 03/11/2018 22.31, ellanios82 wrote:
a week ago , upon completion of doing my weekly "zypper dup" , running "updatedb" got stuck and continued running `forever` - same today : "updatedb" got stuck Is that tumbleweed? - Yes : that is TW
..........
rgds Could you provide some more info? Running TW here, no issues running updatedb. For instance, paste the output of "df -h".
Then, kill the process and run it on a terminal. "su - nobody" then run it. See if there are messages.
- run in init 3 state : impossible to kill updatedb
Is that the exact output message when trying to kill updatedb, or is it some description? If the later, try to be more verbose, because it is inintelligible. But I would prefer to see the command and the result. Like: Telcontar:~ # killall updatedb updatedb: no process found Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 04/11/2018 05:05, Carlos E. R. wrote:
On 03/11/2018 23.53, ellanios82 wrote:
On 04/11/2018 00:10, Carlos E. R. wrote:
On 03/11/2018 23.03, Knurpht-openSUSE wrote:
Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82:
On 03/11/2018 23:43, Carlos E. R. wrote:
On 03/11/2018 22.31, ellanios82 wrote: > a week ago , upon completion of doing my weekly "zypper dup" , > running > "updatedb" got stuck and continued running `forever` > - same today : "updatedb" got stuck Is that tumbleweed? - Yes : that is TW
..........
rgds Could you provide some more info? Running TW here, no issues running updatedb. For instance, paste the output of "df -h".
Then, kill the process and run it on a terminal. "su - nobody" then run it. See if there are messages.
- run in init 3 state : impossible to kill updatedb Is that the exact output message when trying to kill updatedb, or is it some description? If the later, try to be more verbose, because it is inintelligible. But I would prefer to see the command and the result.
Like:
Telcontar:~ # killall updatedb updatedb: no process found Telcontar:~ #
- no , no message at all : had to `shutdown --reboot`after logging-in as root on F2 ...... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 04/11/2018 à 08:20, ellanios82 a écrit :
- no , no message at all : had to `shutdown --reboot`after logging-in as root on F2
oh... no "kill" possible? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/11/2018 10:02, jdd@dodin.org wrote:
Le 04/11/2018 à 08:20, ellanios82 a écrit :
- no , no message at all : had to `shutdown --reboot`after logging-in as root on F2
oh... no "kill" possible?
jdd
- correct : no kill possible ...... rgds -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 04/11/2018 à 12:01, ellanios82 a écrit :
On 04/11/2018 10:02, jdd@dodin.org wrote:
Le 04/11/2018 à 08:20, ellanios82 a écrit :
- no , no message at all : had to `shutdown --reboot`after logging-in as root on F2
oh... no "kill" possible?
jdd
- correct : no kill possible
what gives "pas ax" as root on the second terminal? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 04/11/2018 à 12:05, jdd@dodin.org a écrit :
Le 04/11/2018 à 12:01, ellanios82 a écrit :
what gives "pas ax" as root on the second terminal?
sorry "ps ax" jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/11/2018 12.01, ellanios82 wrote:
On 04/11/2018 10:02, jdd@dodin.org wrote:
Le 04/11/2018 à 08:20, ellanios82 a écrit :
- no , no message at all : had to `shutdown --reboot`after logging-in as root on F2
oh... no "kill" possible?
jdd
- correct : no kill possible
Again, please, details. Not one sentence per email. You used kill or killall? Did the command return or not? If not, how long did you wait? If yes, any message? Either way, what was on the log? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 04/11/2018 08.20, ellanios82 wrote:
On 04/11/2018 05:05, Carlos E. R. wrote:
On 03/11/2018 23.53, ellanios82 wrote:
On 04/11/2018 00:10, Carlos E. R. wrote:
On 03/11/2018 23.03, Knurpht-openSUSE wrote:
Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82:
On 03/11/2018 23:43, Carlos E. R. wrote: > On 03/11/2018 22.31, ellanios82 wrote: >> a week ago , upon completion of doing my weekly "zypper dup" , >> running >> "updatedb" got stuck and continued running `forever` >> - same today : "updatedb" got stuck > Is that tumbleweed? - Yes : that is TW
..........
rgds Could you provide some more info? Running TW here, no issues running updatedb. For instance, paste the output of "df -h".
Then, kill the process and run it on a terminal. "su - nobody" then run it. See if there are messages.
- run in init 3 state : impossible to kill updatedb Is that the exact output message when trying to kill updatedb, or is it some description? If the later, try to be more verbose, because it is inintelligible. But I would prefer to see the command and the result.
Like:
Telcontar:~ # killall updatedb updatedb: no process found Telcontar:~ #
- no , no message at all : had to `shutdown --reboot`after logging-in as root on F2
That does not make sense. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 04/11/2018 00:03, Knurpht-openSUSE wrote: > Op zaterdag 3 november 2018 22:48:31 CET schreef ellanios82: >> On 03/11/2018 23:43, Carlos E. R. wrote: >>> On 03/11/2018 22.31, ellanios82 wrote: >>>> a week ago , upon completion of doing my weekly "zypper dup" , running >>>> "updatedb" got stuck and continued running `forever` >>>> >>>> >>>> - same today : "updatedb" got stuck >>> Is that tumbleweed? >> - Yes : that is TW >> >> >> .......... >> >> rgds > Could you provide some more info? > Running TW here, no issues running updatedb. > > this happens in init 3 logged-in as root. and run immediately the moment zypper dup has completed : when running updatedb from Konsole on XFCE , as root : No probs : runs fast and completes tidily. ....... rgds -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
ellanios82 -
jdd＠dodin.org -
Knurpht-openSUSE -
Patrick Shanahan