Problem after running portupgrade (continue)

2004-05-26 Thread Stephen Liu
Hi folks,

I found following files on

# ls -lh /tmp/
srwxrwxrwx  1 wnn  wheel   0B Mar 28 23:22
cd_sockV4
srwxr-xr-x  1 satimis  wheel   0B May 25 19:33
file1XG2EX
srwxr-xr-x  1 satimis  wheel   0B May 25 22:37
file38j0wR
srwxr-xr-x  1 satimis  wheel   0B May 23 23:41
file4Umjgt
srwxr-xr-x  1 satimis  wheel   0B May 24 23:03
fileBSC8C0
srwxr-xr-x  1 satimis  wheel   0B May 24 23:41
fileQJVrqc
srwxr-xr-x  1 satimis  wheel   0B May 23 20:04
fileZZ7EKb
srwxr-xr-x  1 satimis  wheel   0B May 23 00:27
fileZzv73Y
srwxr-xr-x  1 satimis  wheel   0B May 27 09:01
filedInBFW
srwxr-xr-x  1 satimis  wheel   0B May 25 15:40
filehXKshb
srwxr-xr-x  1 satimis  wheel   0B May 26 23:47
filel6qaBo
srwxr-xr-x  1 satimis  wheel   0B May 23 00:29
filelVIjRu
srwxr-xr-x  1 satimis  wheel   0B May 25 23:37
fileq1kqeJ
srwxr-xr-x  1 satimis  wheel   0B May 23 19:57
fileqqmG1v
srwxr-xr-x  1 satimis  wheel   0B May 25 13:08
filercSbq1
srwxr-xr-x  1 satimis  wheel   0B May 23 08:15
fileshMHVV
srwxr-xr-x  1 satimis  wheel   0B May 26 00:09
filewt72dp

But they can't be moved to /urs/tmp

Any advise?  What are they for and how they were
created.  Can I delete them all

TIA

B.R.
Stephen Liu

___
Do You Yahoo!?
Get your free @yahoo.com.hk address at http://mail.english.yahoo.com.hk
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem after running portupgrade

2004-05-25 Thread Stephen Liu
Hi Chris,

Tks for your advice.
 
 Look into /var/log for a list of files like this
 example:
 
 cron.0.bz2  maillog.1.bz2  
 sendmail.st.0
 cron.1.bz2  maillog.2.bz2  
 sendmail.st.1
 
 Note the bz2 extensions and the files that have
 digits  at the end.
 Chances are you may have many. You can delete these
 if you wish.

ls /var/log/
XFree86.0-1.log messages.0.bz2
XFree86.0-2.log messages.1.bz2
XFree86.0-2.log~messages.2.bz2
XFree86.0-3.log messages.3.bz2
XFree86.0.log   messages.4.bz2
XFree86.0.log.old   messages.5.bz2
XFree86.0.log~  mount.today
XFree86.8-1.log ppp.log
XFree86.8.log   ppp.log.0.bz2
XFree86.8.log.old   ppp.log.1.bz2
XFree86.8.log~  ppp.log.2.bz2
auth.logppp.log.3.bz2
auth.log.0.bz2  ppp.log~
cronppp.yd_040225
cron.0.bz2  scrollkeeper.log
cron.1.bz2  security
cron.2.bz2  sendmail.st
cron.3.bz2  sendmail.st.0
cupssendmail.st.1
debug.log   sendmail.st.10
dmesg.today sendmail.st.2
dmesg.yesterday sendmail.st.3
kdm.log sendmail.st.4
lastlog sendmail.st.5
lpd-errssendmail.st.6
maillog sendmail.st.7
maillog.0.bz2   sendmail.st.8
maillog.1.bz2   sendmail.st.9
maillog.2.bz2   setuid.today
maillog.3.bz2   setuid.yesterday
maillog.4.bz2   slip.log
maillog.5.bz2   userlog
maillog.6.bz2   wtmp
maillog.7.bz2   xdm.log
messagesxferlog

I am going to delete following files;

/var/log/
messages.0.bz2
messages.1.bz2
messages.2.bz2
messages.3.bz2
messages.4.bz2
messages.5.bz2
ppp.log.0.bz2
ppp.log.1.bz2
ppp.log.2.bz2
ppp.log.3.bz2
auth.log.0.bz2
cron.0.bz2
cron.1.bz2
cron.2.bz2
cron.3.bz2
sendmail.st.1
sendmail.st.10
sendmail.st.2
sendmail.st.3
sendmail.st.4
sendmail.st.5
sendmail.st.6
sendmail.st.7
sendmail.st.8
sendmail.st.9
maillog.0.bz2
maillog.1.bz2
maillog.2.bz2
maillog.3.bz2
maillog.4.bz2
maillog.5.bz2
maillog.6.bz2
maillog.7.bz2

Any comment ???

 Also, look around the dirs within /var  You may have
 something logging such as 
 a core dump.

$ ls /var
account db  log rwho
at  empty   mailspool
backups games   msgstmp
crash   heimdal preserveyp
cronlib run

$ ls /var/backups
aliases.bak master.passwd.bak
group.bak   master.passwd.bak2
group.bak2

Can I delete all above files ???

$ ls /var/tmp
gconfd-root svh3k.tmp
gconfd-satimis  svh3m.tmp
linux_base-7.1_5.tbzsvmhc.tmp
mapping-rootsvmhe.tmp
mapping-satimis svmhg.tmp
orbit-root  teTeX-2.0.2_2.tbz
orbit-satimis   tmp.0.QQlif7
pkgdb.fixme tmp.0.dr0vBP
sv603.tmp   tmp.0.kDy79T
sv605.tmp   tmp.0.lu8h4X
sv607.tmp   tmp.1.Egne6s
svd5k.tmp   tmp.1.JW15qD
svd5m.tmp   tmp.1.nNXAdw
svd5o.tmp   tmp.1.xygGQv
svh3i.tmp   vi.recover

Can I delete above files with .tmp extension and all
tmp files ???

# ls /var/cron
tabs

# ls /var/run
cron.pid
.

core dump
could not be found

B.R.
Stephen

___
Do You Yahoo!?
Get your free @yahoo.com.hk address at http://mail.english.yahoo.com.hk
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem after running portupgrade

2004-05-25 Thread Stephen Liu
Hi Remko,

Tks for your advice.

 It says to you that the var drive is full, the var
 drive keeps logs etc 
 so pretty crucial that it has some space. Go to
 /var/log and check which 
 files are a bit big and rotate them. You can do
 that by entering 
 single user mode, mount the /var, go to /var/log,
 type `ls -lh' it gives
 you the filesizes
 
 Some file has to be what bigger then the rest, so we
 need to clean it a bit.
 Mount the /usr drive and create the directory
 /usr/tmp (since that drive 
 has a lot of space left), now mv
 /var/log/$bigfilename /usr/tmp/ and
 touch /var/log/$bigfilename (So that it does exist).

It is not the files on /var/log/ taking up space but
following files on /var/tmp/

# ls -lh
total 192544
-rw-r--r--  1 satimis  wheel  2.3M May 14 22:26
tmp.0.QQlif7
-rw-r--r--  1 satimis  wheel  2.3M May 14 22:24
tmp.0.dr0vBP
-rw-r--r--  1 satimis  wheel  2.3M May 15 15:58
tmp.0.kDy79T
-rw-r--r--  1 satimis  wheel  2.3M May 14 22:29
tmp.0.lu8h4X
-rw-r--r--  1 satimis  wheel   26M May 14 22:26
tmp.1.Egne6s
-rw-r--r--  1 satimis  wheel   72M May 14 22:25
tmp.1.JW15qD
-rw-r--r--  1 satimis  wheel   32M May 14 22:29
tmp.1.nNXAdw
-rw-r--r--  1 satimis  wheel   48M May 15 15:59
tmp.1.xygGQv
.

I have no idea what they are and when they were
created.

# df
Filesystem  1K-blocksUsedAvail Capacity 
Mounted on
/dev/ad4s1a253678   45872   18751220%/
devfs   1   10   100%/dev
/dev/ad4s1e2536784672   228712 2%/tmp
/dev/ad4s1f  36354884 4807654 2863884014%/usr
/dev/ad4s1d253678   57664   17572025%/var

 If you reboot now the system will come up and i
 guess that the things 
 are starting to work again.
 
 The Failure of gnome is too less space on /var i
 think,

After rebooting the PC, Gnome revived.  Still have
some minor problems, such as on KDE desktop Konsole
window, selected fonts unable to save (saving settings
having no function)

 The portsclean package? What's that? Search the
 internet

'portsclean' is an utility of 'portupgrade'.  Very
powerful taking about 5 minute to complete on my slow
system.  Now it got lost.  I think I have to reinstall
'portupgrade'

 Try changing your settings in Konsole now, perhaps
 there is enough space 
 now.

Still having problem.  Please see above.

Tks again for your advice.

B.R.
Stephen

___
Do You Yahoo!?
Get your free @yahoo.com.hk address at http://mail.english.yahoo.com.hk
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Problem after running portupgrade

2004-05-24 Thread Stephen Liu
Hi folks,

I encountered problems after running

# portupgrade -aRrvO

At completion following warning popup;
.
..
Backing up the old version

/var: write failed, filesystem is full

bzip2: I/O or other error, bailing out.  Possible
reason follows.
bzip2: No space left on device
Input file = (stdin), output file = (stdout)
** Backup failed.
---  Uninstallation of linux_base-7.1_5 ended at:
Mon, 24 May 2004 22:20:19 +0800 (consumed 00:00:09)
---  Upgrade of emulators/linux_base ended at: Mon,
24 May 2004 22:20:19 +0800 (consumed 00:18:22)
[Updating the pkgdb format:dbm_hash in /var/db/pkg
... - 260 packages found (-0 +2) ..
/var: write failed, filesystem is full
---  Session ended at: Mon, 24 May 2004 22:20:22
+0800 (consumed 20:46:59)
/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:241:in
`origin': dbm_store failed: Cannot update the pkgdb!]
(PkgDB:BError)
from
/usr/local/lib/ruby/site_ruby/1.6/pkginfo.rb:178:in
`origin'
from /usr/local/sbin/portupgrade:709:in
`do_upgrade'
from /usr/local/sbin/portupgrade:686:in `main'
from /usr/local/sbin/portupgrade:685:in `each'
from /usr/local/sbin/portupgrade:685:in `main'
from /usr/local/sbin/portupgrade:207:in
`initialize'
from /usr/local/sbin/portupgrade:207:in `new'
from /usr/local/sbin/portupgrade:207:in `main'
from /usr/local/sbin/portupgrade:1846
#

Reboot PC. Gnome could not be started with a warning
something like server configure error.

I have no chance to write down the complete warning
because it jumped to another empty window after a
while. Nor I have an editor to copy the warning down.

KDE started properly. Following problems were found.

1)
# /usr/src/etc/periodic/weekly/310.locate updatedb

Rebuilding locate database:
/var: write failed, filesystem is full
cat: stdout: No space left on device

2)
# df

Filesystem  1K-blocksUsedAvail Capacity 
Mounted on
/dev/ad4s1a253678   45872   18751220%/
devfs   1   10   100%/dev
/dev/ad4s1e2536784672   228712 2%/tmp
/dev/ad4s1f  36354884 4619692 2882680214%/usr
/dev/ad4s1d253678  249478   -16094   107%/var

3)
# portsclean -C
portsclean: Command not found

# cd /usr/ports
# make search name=portsclean
No printout

4) On KDE desktop
Konsole window - Font characters being huge
Settings - Font - Custom
started 'request font' window. It was possible to
select font.

But
Settings - Save Settings
seemed having no function. On starting a new Konsole
window fonts were still huge.

That were the mistakes having been discovered. Others
unknown yet.

Kindly advise.
1) How to free space. The HD is of 40 G in size solely
for FreeBSD 5.2
2) Where can I find 'portsclean' package
3) How to discover the cause of failure in starting
Gnome
4) How to set fonts on Konsole window

TIA

B.R.
Stephen Liu

___
Do You Yahoo!?
Get your free @yahoo.com.hk address at http://mail.english.yahoo.com.hk
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem after running portupgrade

2004-05-24 Thread Chris
On Monday 24 May 2004 11:49 am, Stephen Liu wrote:
 Hi folks,

 I encountered problems after running

 # portupgrade -aRrvO

 At completion following warning popup;
 .
 ..
 Backing up the old version

 /var: write failed, filesystem is full

Look into /var/log for a list of files like this example:


cron.0.bz2  maillog.1.bz2   sendmail.st.0
cron.1.bz2  maillog.2.bz2   sendmail.st.1

Note the bz2 extensions and the files that have digits  at the end.
Chances are you may have many. You can delete these if you wish.

Also, look around the dirs within /var  You may have something logging such as 
a core dump.

Just a thought.

-- 
Best regards,
Chris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problem after running portupgrade

2004-05-24 Thread Remko Lodder
Hey again Stephen,
Stephen Liu wrote:
Hi folks,
I encountered problems after running
# portupgrade -aRrvO
At completion following warning popup;
.
..
Backing up the old version
/var: write failed, filesystem is full
bzip2: I/O or other error, bailing out.  Possible
reason follows.
bzip2: No space left on device
Input file = (stdin), output file = (stdout)
** Backup failed.
---  Uninstallation of linux_base-7.1_5 ended at:
Mon, 24 May 2004 22:20:19 +0800 (consumed 00:00:09)
---  Upgrade of emulators/linux_base ended at: Mon,
24 May 2004 22:20:19 +0800 (consumed 00:18:22)
[Updating the pkgdb format:dbm_hash in /var/db/pkg
... - 260 packages found (-0 +2) ..
/var: write failed, filesystem is full
---  Session ended at: Mon, 24 May 2004 22:20:22
+0800 (consumed 20:46:59)
/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:241:in
`origin': dbm_store failed: Cannot update the pkgdb!]
(PkgDB:BError)
from
/usr/local/lib/ruby/site_ruby/1.6/pkginfo.rb:178:in
`origin'
from /usr/local/sbin/portupgrade:709:in
`do_upgrade'
from /usr/local/sbin/portupgrade:686:in `main'
from /usr/local/sbin/portupgrade:685:in `each'
from /usr/local/sbin/portupgrade:685:in `main'
from /usr/local/sbin/portupgrade:207:in
`initialize'
from /usr/local/sbin/portupgrade:207:in `new'
from /usr/local/sbin/portupgrade:207:in `main'
from /usr/local/sbin/portupgrade:1846
#
Reboot PC. Gnome could not be started with a warning
something like server configure error.
I have no chance to write down the complete warning
because it jumped to another empty window after a
while. Nor I have an editor to copy the warning down.
KDE started properly. Following problems were found.
1)
# /usr/src/etc/periodic/weekly/310.locate updatedb
Rebuilding locate database:
/var: write failed, filesystem is full
cat: stdout: No space left on device
2)
# df
Filesystem  1K-blocksUsedAvail Capacity 
Mounted on
/dev/ad4s1a253678   45872   18751220%/
devfs   1   10   100%/dev
/dev/ad4s1e2536784672   228712 2%/tmp
/dev/ad4s1f  36354884 4619692 2882680214%/usr
/dev/ad4s1d253678  249478   -16094   107%/var

3)
# portsclean -C
portsclean: Command not found
# cd /usr/ports
# make search name=portsclean
No printout
4) On KDE desktop
Konsole window - Font characters being huge
Settings - Font - Custom
started 'request font' window. It was possible to
select font.
But
Settings - Save Settings
seemed having no function. On starting a new Konsole
window fonts were still huge.
That were the mistakes having been discovered. Others
unknown yet.
Kindly advise.
1) How to free space. The HD is of 40 G in size solely
for FreeBSD 5.2
2) Where can I find 'portsclean' package
3) How to discover the cause of failure in starting
Gnome
4) How to set fonts on Konsole window
TIA
B.R.
Stephen Liu
Ofcourse you searched the internet, the archives etc? (guess not)
It says to you that the var drive is full, the var drive keeps logs etc 
so pretty crucial that it has some space. Go to /var/log and check which 
files are a bit big and rotate them. You can do that by entering 
single user mode, mount the /var, go to /var/log, type `ls -lh' it gives
you the filesizes

Some file has to be what bigger then the rest, so we need to clean it a bit.
Mount the /usr drive and create the directory /usr/tmp (since that drive 
has a lot of space left), now mv /var/log/$bigfilename /usr/tmp/ and
touch /var/log/$bigfilename (So that it does exist).

If you reboot now the system will come up and i guess that the things 
are starting to work again.

The Failure of gnome is too less space on /var i think,
The portsclean package? What's that? Search the internet ;)
Try changing your settings in Konsole now, perhaps there is enough space 
now.


--
Kind regards,
Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl Dutch community for helping newcomers on the 
hackerscene
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]