
20th June 2010, 18:34
|
|
Senior Member
|
|
Join Date: Feb 2009
Posts: 250
Thanks: 71
Thanked 5 Times in 4 Posts
|
|
Problem with upgrade
Hello
After upgrade from 9.10 to 10.04 I try to aptitude upgrade and have following log:
Code:
The following packages have unmet dependencies:
linux-restricted-modules-2.6.27-17-server: Depends: linux-restricted-modules-c
linux-restricted-modules-2.6.28-18-server: Depends: linux-restricted-modules-c
I can aptitude -f install but have this log:
Code:
root@itex:~# aptitude -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages are BROKEN:
libdate-manip-perl linux-restricted-modules-2.6.27-17-server
linux-restricted-modules-2.6.28-18-server
The following NEW packages will be installed:
libnet-snmp-perl librrd4 librrds-perl rrdtool
The following packages will be REMOVED:
autoconf2.13{u} automake1.4{u} binutils-static{u} bsd-mailx{u}
libbind9-50{u} libc-client2007b{u} libcompress-bzip2-perl{u}
libdjvulibre-text{u} libdjvulibre21{u} libdns53{u} libgraphviz4{u}
libilmbase6{u} libisc50{u} libisccc50{u} libisccfg50{u} liblwres50{u}
libmhash2{u} libming0{u} libntfs-3g54{u} libopenexr6{u} libsensors3{u}
libwmf0.2-7{u}
0 packages upgraded, 5 newly installed, 22 to remove and 0 not upgraded.
Need to get 3,152kB of archives. After unpacking 1,561kB will be used.
The following packages have unmet dependencies:
linux-restricted-modules-2.6.27-17-server: Depends: linux-restricted-modules-common which is a virtual package.
linux-restricted-modules-2.6.28-18-server: Depends: linux-restricted-modules-common which is a virtual package.
libdate-manip-perl: Depends: libyaml-syck-perl but it is not installable
The following actions will resolve these dependencies:
Remove the following packages:
linux-restricted-modules-2.6.27-17-server
linux-restricted-modules-2.6.28-18-server
Keep the following packages at their current version:
libdate-manip-perl [Not Installed]
Score is 257
Accept this solution? [Y/n/q/?] q
If I aptitude -f install after that all be ok with ISPConfig2 and my server?
Thnk you!
|

21st June 2010, 14:40
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,665
Thanks: 1,896
Thanked 2,594 Times in 2,445 Posts
|
|
I don't think this will cause problems for ISPConfig.
|
|
The Following User Says Thank You to falko For This Useful Post:
|
|

28th June 2010, 16:29
|
|
Senior Member
|
|
Join Date: Feb 2009
Posts: 250
Thanks: 71
Thanked 5 Times in 4 Posts
|
|
Yes its ok.
But after ISPConfig upgrade and dist upgrade web-ftp in ISPConfig dont work.
Simple FTP work only in active mode.
How to decide this problem?
And in kern.log have this:
Code:
Jun 27 06:57:28 itex kernel: [459924.717658] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.133958] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.134240] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.134519] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.134789] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.135079] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.135358] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.135640] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.135921] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.136194] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.136469] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.137778] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.138077] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.138357] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.138636] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.138936] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.139210] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.139480] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.139763] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.140039] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.140327] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.141578] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.141876] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Jun 27 07:26:49 itex kernel: [461685.142161] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00000010 - Ch 1
Thnk you for help!
|

29th June 2010, 13:51
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,665
Thanks: 1,896
Thanked 2,594 Times in 2,445 Posts
|
|
Seems to be a firewall problem. What's the output of ?
|

29th June 2010, 13:57
|
|
Senior Member
|
|
Join Date: Feb 2009
Posts: 250
Thanks: 71
Thanked 5 Times in 4 Posts
|
|
Output is:
Code:
root@itex:~# iptables -L
Chain INPUT (policy DROP)
target prot opt source destination
DROP tcp -- anywhere loopback/8
ACCEPT all -- anywhere anywhere state RELATED,ESTAB LISHED
ACCEPT all -- anywhere anywhere
DROP all -- BASE-ADDRESS.MCAST.NET/4 anywhere
PUB_IN all -- anywhere anywhere
PUB_IN all -- anywhere anywhere
PUB_IN all -- anywhere anywhere
PUB_IN all -- anywhere anywhere
DROP all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTAB LISHED
DROP all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
PUB_OUT all -- anywhere anywhere
PUB_OUT all -- anywhere anywhere
PUB_OUT all -- anywhere anywhere
PUB_OUT all -- anywhere anywhere
Chain INT_IN (0 references)
target prot opt source destination
ACCEPT icmp -- anywhere anywhere
DROP all -- anywhere anywhere
Chain INT_OUT (0 references)
target prot opt source destination
ACCEPT icmp -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain PAROLE (10 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
Chain PUB_IN (4 references)
target prot opt source destination
ACCEPT icmp -- anywhere anywhere icmp destination-un reachable
ACCEPT icmp -- anywhere anywhere icmp echo-reply
ACCEPT icmp -- anywhere anywhere icmp time-exceeded
ACCEPT icmp -- anywhere anywhere icmp echo-request
PAROLE tcp -- anywhere anywhere tcp dpt:ftp
PAROLE tcp -- anywhere anywhere tcp dpt:ssh
PAROLE tcp -- anywhere anywhere tcp dpt:smtp
PAROLE tcp -- anywhere anywhere tcp dpt:domain
PAROLE tcp -- anywhere anywhere tcp dpt:www
PAROLE tcp -- anywhere anywhere tcp dpt:81
PAROLE tcp -- anywhere anywhere tcp dpt:pop3
PAROLE tcp -- anywhere anywhere tcp dpt:imap2
PAROLE tcp -- anywhere anywhere tcp dpt:https
PAROLE tcp -- anywhere anywhere tcp dpt:webmin
ACCEPT udp -- anywhere anywhere udp dpt:domain
DROP icmp -- anywhere anywhere
DROP all -- anywhere anywhere
Chain PUB_OUT (4 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
In router 21 port open too.
|

30th June 2010, 15:02
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,665
Thanks: 1,896
Thanked 2,594 Times in 2,445 Posts
|
|
Can you switch off the firewall for testing purposes? Does it work then?
|

2nd July 2010, 12:25
|
|
Senior Member
|
|
Join Date: Feb 2009
Posts: 250
Thanks: 71
Thanked 5 Times in 4 Posts
|
|
I am trying to stop IP tables with this script:
Code:
# iptables -X
# iptables -t nat -F
# iptables -t nat -X
# iptables -t mangle -F
# iptables -t mangle -X
# iptables -P INPUT ACCEPT
# iptables -P FORWARD ACCEPT
# iptables -P OUTPUT ACCEPT
After:
Code:
root@itex:/# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
After this command I restart ISPConfig
and restart Porftpd too.
But problem still not decided.
|

3rd July 2010, 11:58
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,665
Thanks: 1,896
Thanked 2,594 Times in 2,445 Posts
|
|
|

4th July 2010, 11:45
|
|
Senior Member
|
|
Join Date: Feb 2009
Posts: 250
Thanks: 71
Thanked 5 Times in 4 Posts
|
|
Output is:
Code:
root@itex:~# netstat -tap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:40421 *:* LISTEN 3990/portsentry
tcp 0 0 *:32773 *:* LISTEN 3990/portsentry
tcp 0 0 *:32774 *:* LISTEN 3990/portsentry
tcp 0 0 *:31337 *:* LISTEN 3990/portsentry
tcp 0 0 *:mysql *:* LISTEN 746/mysqld
tcp 0 0 *:ircd *:* LISTEN 3990/portsentry
tcp 0 0 *:systat *:* LISTEN 3990/portsentry
tcp 0 0 *:5742 *:* LISTEN 3990/portsentry
tcp 0 0 *:sunrpc *:* LISTEN 3990/portsentry
tcp 0 0 *:finger *:* LISTEN 3990/portsentry
tcp 0 0 *:netstat *:* LISTEN 3990/portsentry
tcp 0 0 *:www *:* LISTEN 14946/apache2
tcp 0 0 *:webmin *:* LISTEN 4420/perl
tcp 0 0 *:54320 *:* LISTEN 3990/portsentry
tcp 0 0 *:cisco-sccp *:* LISTEN 3990/portsentry
tcp 0 0 *:81 *:* LISTEN 3154/ispconfig_http
tcp 0 0 *:27665 *:* LISTEN 3990/portsentry
tcp 0 0 *:ingreslock *:* LISTEN 3990/portsentry
tcp 0 0 *:ftp *:* LISTEN 31564/proftpd: (acc
tcp 0 0 ns.domain:domain *:* LISTEN 3439/named
tcp 0 0 itex.domain:domain *:* LISTEN 3439/named
tcp 0 0 localhost.locald:domain *:* LISTEN 3439/named
tcp 0 0 *:ssh *:* LISTEN 754/sshd
tcp 0 0 *:nntp *:* LISTEN 3990/portsentry
tcp 0 0 *:socks *:* LISTEN 3990/portsentry
tcp 0 0 *:smtp *:* LISTEN 19711/master
tcp 0 0 localhost.localdoma:953 *:* LISTEN 3439/named
tcp 0 0 *:12345 *:* LISTEN 3990/portsentry
tcp 0 0 *:12346 *:* LISTEN 3990/portsentry
tcp 0 0 *:https *:* LISTEN 14946/apache2
tcp 0 0 *:635 *:* LISTEN 3990/portsentry
tcp 0 0 *:49724 *:* LISTEN 3990/portsentry
tcp 0 0 *:uucp *:* LISTEN 3990/portsentry
tcp 0 0 localhost.localdo:60000 *:* LISTEN 1600/postgrey.pid -
tcp 0 0 *:tcpmux *:* LISTEN 3990/portsentry
tcp 0 0 *:20034 *:* LISTEN 3990/portsentry
tcp 0 0 *:32771 *:* LISTEN 3990/portsentry
tcp 0 0 *:32772 *:* LISTEN 3990/portsentry
tcp6 0 0 [::]:pop3 [::]:* LISTEN 1894/couriertcpd
tcp6 0 0 [::]:imap2 [::]:* LISTEN 1860/couriertcpd
tcp6 0 0 [::]:ssh [::]:* LISTEN 754/sshd
tcp6 0 0 [::]:smtp [::]:* LISTEN 19711/master
tcp6 0 0 localhost:953 [::]:* LISTEN 3439/named
tcp6 0 0 [::]:imaps [::]:* LISTEN 1880/couriertcpd
tcp6 0 0 [::]:pop3s [::]:* LISTEN 1922/couriertcpd
|

5th July 2010, 17:55
|
|
Super Moderator
|
|
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,665
Thanks: 1,896
Thanked 2,594 Times in 2,445 Posts
|
|
Hm, looks ok. Can you post your /etc/proftpd/proftpd.conf?
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT +2. The time now is 08:30.
|
|
Recent comments
1 day 8 hours ago
1 day 8 hours ago
1 day 13 hours ago
1 day 20 hours ago
1 day 21 hours ago
1 day 22 hours ago
2 days 2 hours ago
2 days 9 hours ago
2 days 13 hours ago
2 days 14 hours ago