[SAC] trac VM in unhealthy state

hi SAC,

I have restarted right now Apache on trac to make it responsive again.

dmesg shows unhealthy messages, need to restart the machine?

Markus

PS: dmesg
...
[14618173.629688] BUG: soft lockup - CPU#1 stuck for 61s! [apache2:19038]
[14618173.689708] Modules linked in: ipv6 loop snd_pcsp snd_pcm
snd_timer snd soundcore psmouse i2c_piix4 serio_raw virtio_net button
parport_pc parport i2c_core snd_page_alloc joydev evdev ext3 jbd
mbcache ide_cd_mod cdrom usbhid hid ff_memless piix ide_pci_generic
ide_core ata_generic libata virtio_blk scsi_mod dock virtio_pci
virtio_ring floppy virtio uhci_hcd thermal processor fan thermal_sys
[last unloaded: scsi_wait_scan]
[14618173.689708] CPU 1:
[14618173.689708] Modules linked in: ipv6 loop snd_pcsp snd_pcm
snd_timer snd soundcore psmouse i2c_piix4 serio_raw virtio_net button
parport_pc parport i2c_core snd_page_alloc joydev evdev ext3 jbd
mbcache ide_cd_mod cdrom usbhid hid ff_memless piix ide_pci_generic
ide_core ata_generic libata virtio_blk scsi_mod dock virtio_pci
virtio_ring floppy virtio uhci_hcd thermal processor fan thermal_sys
[last unloaded: scsi_wait_scan]
[14618173.689708] Pid: 19038, comm: apache2 Not tainted 2.6.26-2-amd64 #1
[14618173.689708] RIP: 0010:[<ffffffff803234aa>] [<ffffffff803234aa>]
iowrite16+0x24/0x34
[14618173.689708] RSP: 0000:ffff81021f0b7cf8 EFLAGS: 00000206
[14618173.689708] RAX: 0000000000000001 RBX: ffff81017ad0b680 RCX:
ffff81021f0f9000
[14618173.689708] RDX: 000000000000c050 RSI: 000000000001c050 RDI:
0000000000000001
[14618173.689708] RBP: ffff81021f0b7c70 R08: 00000000000000fb R09:
ffff81021f0f9000
[14618173.689708] R10: 0000000000000012 R11: ffffffffa004233f R12:
ffffffff8020cd02
[14618173.689708] R13: ffff81021f0b7c70 R14: ffff81021d9ca700 R15:
0000000000000000
[14618173.689708] FS: 00007f6ac8a0c750(0000)
GS:ffff81021f0908c0(0000) knlGS:0000000000000000
[14618173.689708] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[14618173.689708] CR2: 00007f6ab5aa5008 CR3: 00000000bc3dc000 CR4:
00000000000006e0
[14618173.689708] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[14618173.689708] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[14618173.689708]
[14618173.689708] Call Trace:
[14618173.689708] <IRQ> [<ffffffffa01695a1>] ?
:virtio_net:start_xmit+0xc3/0xca
[14618173.689708] [<ffffffff803ccab7>] ? __qdisc_run+0xc0/0x1b3
[14618173.689708] [<ffffffff803bdd30>] ? dev_queue_xmit+0x179/0x2b1
[14618173.689708] [<ffffffff803c121d>] ? neigh_update+0x30b/0x3e7
[14618173.689708] [<ffffffff803caecf>] ? eth_header_cache_update+0x0/0x14
[14618173.689708] [<ffffffff803fb35e>] ? arp_process+0x50c/0x54e
[14618173.689708] [<ffffffff8024acbe>] ? getnstimeofday+0x39/0x98
[14618173.689708] [<ffffffff80248e40>] ? ktime_get_real+0xc/0x41
[14618173.689708] [<ffffffffa0169ba9>] ? :virtio_net:virtnet_poll+0x1bc/0x2c3
[14618173.689708] [<ffffffff803bd383>] ? net_rx_action+0xab/0x1da
[14618173.689708] [<ffffffff802393e9>] ? __do_softirq+0x5c/0xd1
[14618173.689708] [<ffffffff8021c4ec>] ? ack_apic_level+0x53/0xd8
[14618173.689708] [<ffffffff8020d2dc>] ? call_softirq+0x1c/0x28
[14618173.689708] [<ffffffff8020f3e8>] ? do_softirq+0x3c/0x81
[14618173.689708] [<ffffffff80239347>] ? irq_exit+0x3f/0x85
[14618173.689708] [<ffffffff8020f648>] ? do_IRQ+0xb9/0xd9
[14618173.689708] [<ffffffff8020c47d>] ? ret_from_intr+0x0/0x19
[14618173.689708] <EOI>
[14767760.870272] BUG: soft lockup - CPU#3 stuck for 61s! [apache2:21062]
[14767760.870272] Modules linked in: ipv6 loop snd_pcsp snd_pcm
snd_timer snd soundcore psmouse i2c_piix4 serio_raw virtio_net button
parport_pc parport i2c_core snd_page_alloc joydev evdev ext3 jbd
mbcache ide_cd_mod cdrom usbhid hid ff_memless piix ide_pci_generic
ide_core ata_generic libata virtio_blk scsi_mod dock virtio_pci
virtio_ring floppy virtio uhci_hcd thermal processor fan thermal_sys
[last unloaded: scsi_wait_scan]
[14767760.870272] CPU 3:
[14767760.870272] Modules linked in: ipv6 loop snd_pcsp snd_pcm
snd_timer snd soundcore psmouse i2c_piix4 serio_raw virtio_net button
parport_pc parport i2c_core snd_page_alloc joydev evdev ext3 jbd
mbcache ide_cd_mod cdrom usbhid hid ff_memless piix ide_pci_generic
ide_core ata_generic libata virtio_blk scsi_mod dock virtio_pci
virtio_ring floppy virtio uhci_hcd thermal processor fan thermal_sys
[last unloaded: scsi_wait_scan]
[14767760.870272] Pid: 21062, comm: apache2 Not tainted 2.6.26-2-amd64 #1
[14767760.870272] RIP: 0010:[<ffffffff8026be45>] [<ffffffff8026be45>]
handle_IRQ_event+0x1e/0x61
[14767760.870272] RSP: 0000:ffff81021f143f38 EFLAGS: 00000246
[14767760.870272] RAX: 0000000000004100 RBX: 000000000000000b RCX:
ffff810080a7c000
[14767760.870272] RDX: 000000000000000b RSI: ffff81021c8344c0 RDI:
000000000000000b
[14767760.870272] RBP: ffff81021f143eb0 R08: 0000000003c9053c R09:
00007f6ac806b9e0
[14767760.870272] R10: 0000000000000001 R11: 0000000000000246 R12:
ffffffff8020cd02
[14767760.870272] R13: ffff81021f143eb0 R14: ffff81021c8344c0 R15:
ffff810001059880
[14767760.870272] FS: 00007f6ac8a0c750(0000)
GS:ffff81021f0a57c0(0000) knlGS:0000000000000000
[14767760.870272] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[14767760.870272] CR2: 00007f6ac8b22000 CR3: 00000002097cf000 CR4:
00000000000006e0
[14767760.870272] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[14767760.870272] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[14767760.870272]
[14767760.870272] Call Trace:
[14767760.870272] <IRQ> [<ffffffff8026d2ea>] ? handle_fasteoi_irq+0x90/0xc8
[14767760.870272] [<ffffffff8020f5fc>] ? do_IRQ+0x6d/0xd9
[14767760.870272] [<ffffffff8020c47d>] ? ret_from_intr+0x0/0x19
[14767760.870272] <EOI>

On Wed, May 22, 2013 at 1:31 PM, Markus Neteler <neteler@osgeo.org> wrote:

hi SAC,

I have restarted right now Apache on trac to make it responsive again.

dmesg shows unhealthy messages, need to restart the machine?

Nobody cares?

Even munin gave up for some hours:
http://webextra.osgeo.osuosl.org/munin/osgeo.org/trac.osgeo.org-apache_accesses.html

Reboot happily?

ciao
Markus

On Thu, May 23, 2013 at 07:57:07AM +0200, Markus Neteler wrote:

Reboot happily?

Definitely, a production system with a stuck CPU is almost always a
good candidate for a reboot :wink:

Cheers,
  Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

On 05/22/2013 11:12 PM, Martin Spott wrote:

On Thu, May 23, 2013 at 07:57:07AM +0200, Markus Neteler wrote:

Reboot happily?

Definitely, a production system with a stuck CPU is almost always a
good candidate for a reboot :wink:

Cheers,
  Martin.

Full restart completed.

Anyone have ideas about what caused the CPU spikes yesterday and today?

Thanks,
Alex

On Thu, May 23, 2013 at 8:22 AM, Alex Mandel <tech_dev@wildintellect.com> wrote:

On 05/22/2013 11:12 PM, Martin Spott wrote:

On Thu, May 23, 2013 at 07:57:07AM +0200, Markus Neteler wrote:

Reboot happily?

Definitely, a production system with a stuck CPU is almost always a
good candidate for a reboot :wink:

Cheers,
        Martin.

Full restart completed.

Anyone have ideas about what caused the CPU spikes yesterday and today?

# For current traffic, use
nethogs eth0

Then I'd suggest to install fail2ban or so:

grep 'Failed password' auth.log auth.log.1 | wc -l
3488
zgrep 'Failed password' auth.log*.gz | wc -l
7486

Markus

Thanks,
Alex

_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac

On 05/22/2013 11:32 PM, Markus Neteler wrote:

On Thu, May 23, 2013 at 8:22 AM, Alex Mandel <tech_dev@wildintellect.com> wrote:

On 05/22/2013 11:12 PM, Martin Spott wrote:

On Thu, May 23, 2013 at 07:57:07AM +0200, Markus Neteler wrote:

Reboot happily?

Definitely, a production system with a stuck CPU is almost always a
good candidate for a reboot :wink:

Cheers,
         Martin.

Full restart completed.

Anyone have ideas about what caused the CPU spikes yesterday and today?

# For current traffic, use
nethogs eth0

Then I'd suggest to install fail2ban or so:

grep 'Failed password' auth.log auth.log.1 | wc -l
3488
zgrep 'Failed password' auth.log*.gz | wc -l
7486

Markus

Thanks,
Alex

That option is fine with me, for some reason thought we had that in the default, guess not. Go ahead and do it.

Anyone have an opinion Fail2ban, DenyHosts or SSHGuard?

Thanks,
Alex

On Wed, May 22, 2013 at 11:38:28PM -0700, Alex Mandel wrote:

Anyone have an opinion Fail2ban, DenyHosts or SSHGuard?

As far as I can tell without checking, "denyhosts" is running on most
of the Debian 6 VM's. If nobody complained, I suspect it's working
properly.

Cheers,
  Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

On Thu, May 23, 2013 at 10:16 AM, Martin Spott <Martin.Spott@mgras.net> wrote:

On Wed, May 22, 2013 at 11:38:28PM -0700, Alex Mandel wrote:

Anyone have an opinion Fail2ban, DenyHosts or SSHGuard?

As far as I can tell without checking, "denyhosts" is running on most
of the Debian 6 VM's. If nobody complained, I suspect it's working
properly.

I guess not:

grep 'Failed password' auth.log auth.log.1 | wc -l
3488
zgrep 'Failed password' auth.log*.gz | wc -l
7486

Many of them are identical IPs... so they are trying dictionary attacks
without being stopped by denyhosts.

Markus

On Thu, May 23, 2013 at 06:24:28PM +0200, Markus Neteler wrote:

On Thu, May 23, 2013 at 10:16 AM, Martin Spott <Martin.Spott@mgras.net> wrote:
> On Wed, May 22, 2013 at 11:38:28PM -0700, Alex Mandel wrote:

>> Anyone have an opinion Fail2ban, DenyHosts or SSHGuard?
>
> As far as I can tell without checking, "denyhosts" is running on most
> of the Debian 6 VM's. If nobody complained, I suspect it's working
> properly.

I guess not:

grep 'Failed password' auth.log auth.log.1 | wc -l
3488
zgrep 'Failed password' auth.log*.gz | wc -l
7486

Note, that the "tracsvn" VM is still running on Debian 5.

Cheers,
  Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

Hi: I am setting up http://lists.osgeo.org/listinfo/pycsw-devel on Nabble [1]. Part of the setup includes importing archives. This step requires URL access to the .mbox.

Can someone point me to the .mbox file?

Thanks

..Tom

[1] http://pycsw-dev.20702.n7.nabble.com/

Hi Tom,

Instead of creating a single forum, don't you prefer to host the
archive at the OSGeo Nabble forum? There is a forum for projects were
most of OSGeo software and data projects are welcome.

http://osgeo-org.1560.x6.nabble.com/OSGeo-Software-and-Data-Projects-f3741872.html

To get the mbox file, logged as admin on mailman you can try

http://lists.osgeo.org/mailman/private/pycsw-devel/pycsw-devel.mbox

Not sure if this works today but it used to. We've asked to Nabble
team for importing mbox files in the past and they usually respond
pretty fast.

Cheers

On 24 May 2013 03:35, Tom Kralidis <tomkralidis@hotmail.com> wrote:

Hi: I am setting up http://lists.osgeo.org/listinfo/pycsw-devel on Nabble [1]. Part of the setup includes importing archives. This step requires URL access to the .mbox.

Can someone point me to the .mbox file?

Thanks

..Tom

[1] http://pycsw-dev.20702.n7.nabble.com/
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac

--
Jorge Sanz
http://es.osgeo.org

Hi Jorge: thanks for the info. Sure, good idea. What needs to happen for http://pycsw-dev.20702.n7.nabble.com/ to be part of OSGeo Nabble? FYI pycsw is an OSGeo project in incubation, so I'm not sure what the inclusion rules are.

FYI, for the mbox file, I was able to find it at http://lists.osgeo.org/mailman/private/pycsw-devel.mbox/pycsw-devel.mbox. However this only includes the last 13 months. Yet the browseable archive (http://lists.osgeo.org/pipermail/pycsw-devel/) has more than that.

Note that we ported the mbox from sf.net to osgeo 13 months ago (see http://trac.osgeo.org/osgeo/ticket/888), so I'm not sure if this is related. Bottom line is that we need a single .mbox for Nabble to import.

Cheers

..Tom

From: jsanz@osgeo.org
Date: Fri, 24 May 2013 06:06:22 +0200
To: sac@lists.osgeo.org
Subject: Re: [SAC] pycsw-devel mbox file for Nabble setup

Hi Tom,

Instead of creating a single forum, don't you prefer to host the
archive at the OSGeo Nabble forum? There is a forum for projects were
most of OSGeo software and data projects are welcome.

http://osgeo-org.1560.x6.nabble.com/OSGeo-Software-and-Data-Projects-f3741872.html

To get the mbox file, logged as admin on mailman you can try

http://lists.osgeo.org/mailman/private/pycsw-devel/pycsw-devel.mbox

Not sure if this works today but it used to. We've asked to Nabble
team for importing mbox files in the past and they usually respond
pretty fast.

Cheers

On 24 May 2013 03:35, Tom Kralidis <tomkralidis@hotmail.com> wrote:

Hi: I am setting up http://lists.osgeo.org/listinfo/pycsw-devel on Nabble [1]. Part of the setup includes importing archives. This step requires URL access to the .mbox.

Can someone point me to the .mbox file?

Thanks

..Tom

[1] http://pycsw-dev.20702.n7.nabble.com/
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac

--
Jorge Sanz
http://es.osgeo.org
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac

Hi sorry for the delay, I was at Geocamp PT in Óbidos :slight_smile:

On 24 May 2013 14:07, Tom Kralidis <tomkralidis@hotmail.com> wrote:

Hi Jorge: thanks for the info. Sure, good idea. What needs to happen for http://pycsw-dev.20702.n7.nabble.com/ to be part of OSGeo Nabble? FYI pycsw is an OSGeo project in incubation, so I'm not sure what the inclusion rules are.

No problem, the only thing to happen is that pcsw project accepts
being archived at OSGeo nabble archive. Being in incubation is indeed
a strong reason.

FYI, for the mbox file, I was able to find it at http://lists.osgeo.org/mailman/private/pycsw-devel.mbox/pycsw-devel.mbox. However this only includes the last 13 months. Yet the browseable archive (http://lists.osgeo.org/pipermail/pycsw-devel/) has more than that.

Note that we ported the mbox from sf.net to osgeo 13 months ago (see http://trac.osgeo.org/osgeo/ticket/888), so I'm not sure if this is related. Bottom line is that we need a single .mbox for Nabble to import.

Well if we can got both mbox files we can ask Nabble team to import
them, I don't see any problem. We just need to provide them links
where they can grab the files.

As your new archive is almost empty, we can just create a new one
under OSGeo forum and ask for the import at Nabble help forum. I'll do
it right now and will wait for your instructions for the mbox import.

--
Jorge Sanz
http://es.osgeo.org

From: jsanz@osgeo.org
Date: Sun, 26 May 2013 19:54:01 +0200
To: sac@lists.osgeo.org
Subject: Re: [SAC] pycsw-devel mbox file for Nabble setup

Hi sorry for the delay, I was at Geocamp PT in Óbidos :slight_smile:

On 24 May 2013 14:07, Tom Kralidis <tomkralidis@hotmail.com> wrote:

Hi Jorge: thanks for the info. Sure, good idea. What needs to happen for http://pycsw-dev.20702.n7.nabble.com/ to be part of OSGeo Nabble? FYI pycsw is an OSGeo project in incubation, so I'm not sure what the inclusion rules are.

No problem, the only thing to happen is that pcsw project accepts
being archived at OSGeo nabble archive. Being in incubation is indeed
a strong reason.

pycsw accepts being archived in OSGeo nabble archive (per https://github.com/geopython/pycsw/issues/152). Thanks.

FYI, for the mbox file, I was able to find it at http://lists.osgeo.org/mailman/private/pycsw-devel.mbox/pycsw-devel.mbox. However this only includes the last 13 months. Yet the browseable archive (http://lists.osgeo.org/pipermail/pycsw-devel/) has more than that.

Note that we ported the mbox from sf.net to osgeo 13 months ago (see http://trac.osgeo.org/osgeo/ticket/888), so I'm not sure if this is related. Bottom line is that we need a single .mbox for Nabble to import.

Well if we can got both mbox files we can ask Nabble team to import
them, I don't see any problem. We just need to provide them links
where they can grab the files.

Both mbox files can be found in http://kralidis.ca/tmp/k/n.tgz. I will delete this location once imported into Nabble.

As your new archive is almost empty, we can just create a new one
under OSGeo forum and ask for the import at Nabble help forum. I'll do
it right now and will wait for your instructions for the mbox import.

OK, I've deleted the pycsw nabble, so the only pycsw devel on nabble is now at http://osgeo-org.1560.x6.nabble.com/pycsw-devel-f5055821.html -- thanks!!

..Tom

--
Jorge Sanz
http://es.osgeo.org
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac

On 26 May 2013 20:19, Tom Kralidis <tomkralidis@hotmail.com> wrote:

From: jsanz@osgeo.org
Date: Sun, 26 May 2013 19:54:01 +0200
To: sac@lists.osgeo.org
Subject: Re: [SAC] pycsw-devel mbox file for Nabble setup

Hi sorry for the delay, I was at Geocamp PT in Óbidos :slight_smile:

On 24 May 2013 14:07, Tom Kralidis <tomkralidis@hotmail.com> wrote:

Hi Jorge: thanks for the info. Sure, good idea. What needs to happen for http://pycsw-dev.20702.n7.nabble.com/ to be part of OSGeo Nabble? FYI pycsw is an OSGeo project in incubation, so I'm not sure what the inclusion rules are.

No problem, the only thing to happen is that pcsw project accepts
being archived at OSGeo nabble archive. Being in incubation is indeed
a strong reason.

pycsw accepts being archived in OSGeo nabble archive (per https://github.com/geopython/pycsw/issues/152). Thanks.

FYI, for the mbox file, I was able to find it at http://lists.osgeo.org/mailman/private/pycsw-devel.mbox/pycsw-devel.mbox. However this only includes the last 13 months. Yet the browseable archive (http://lists.osgeo.org/pipermail/pycsw-devel/) has more than that.

Note that we ported the mbox from sf.net to osgeo 13 months ago (see http://trac.osgeo.org/osgeo/ticket/888), so I'm not sure if this is related. Bottom line is that we need a single .mbox for Nabble to import.

Well if we can got both mbox files we can ask Nabble team to import
them, I don't see any problem. We just need to provide them links
where they can grab the files.

Both mbox files can be found in http://kralidis.ca/tmp/k/n.tgz. I will delete this location once imported into Nabble.

As your new archive is almost empty, we can just create a new one
under OSGeo forum and ask for the import at Nabble help forum. I'll do
it right now and will wait for your instructions for the mbox import.

OK, I've deleted the pycsw nabble, so the only pycsw devel on nabble is now at http://osgeo-org.1560.x6.nabble.com/pycsw-devel-f5055821.html -- thanks!!

..Tom

Perfect,

I've asked for the import[1]. I'll notify here as soon as the files
are imported to the Nabble forum.

Cheers!
[1] http://support.nabble.com/mbox-files-import-td7584587.html

--
Jorge Sanz
http://es.osgeo.org

On 26 May 2013 20:29, Jorge Gaspar Sanz Salinas <jsanz@osgeo.org> wrote:

On 26 May 2013 20:19, Tom Kralidis <tomkralidis@hotmail.com> wrote:

From: jsanz@osgeo.org
Date: Sun, 26 May 2013 19:54:01 +0200
To: sac@lists.osgeo.org
Subject: Re: [SAC] pycsw-devel mbox file for Nabble setup

Hi sorry for the delay, I was at Geocamp PT in Óbidos :slight_smile:

On 24 May 2013 14:07, Tom Kralidis <tomkralidis@hotmail.com> wrote:

Hi Jorge: thanks for the info. Sure, good idea. What needs to happen for http://pycsw-dev.20702.n7.nabble.com/ to be part of OSGeo Nabble? FYI pycsw is an OSGeo project in incubation, so I'm not sure what the inclusion rules are.

No problem, the only thing to happen is that pcsw project accepts
being archived at OSGeo nabble archive. Being in incubation is indeed
a strong reason.

pycsw accepts being archived in OSGeo nabble archive (per https://github.com/geopython/pycsw/issues/152). Thanks.

FYI, for the mbox file, I was able to find it at http://lists.osgeo.org/mailman/private/pycsw-devel.mbox/pycsw-devel.mbox. However this only includes the last 13 months. Yet the browseable archive (http://lists.osgeo.org/pipermail/pycsw-devel/) has more than that.

Note that we ported the mbox from sf.net to osgeo 13 months ago (see http://trac.osgeo.org/osgeo/ticket/888), so I'm not sure if this is related. Bottom line is that we need a single .mbox for Nabble to import.

Well if we can got both mbox files we can ask Nabble team to import
them, I don't see any problem. We just need to provide them links
where they can grab the files.

Both mbox files can be found in http://kralidis.ca/tmp/k/n.tgz. I will delete this location once imported into Nabble.

As your new archive is almost empty, we can just create a new one
under OSGeo forum and ask for the import at Nabble help forum. I'll do
it right now and will wait for your instructions for the mbox import.

OK, I've deleted the pycsw nabble, so the only pycsw devel on nabble is now at http://osgeo-org.1560.x6.nabble.com/pycsw-devel-f5055821.html -- thanks!!

..Tom

Perfect,

I've asked for the import[1]. I'll notify here as soon as the files
are imported to the Nabble forum.

Cheers!
[1] http://support.nabble.com/mbox-files-import-td7584587.html

Archives of pycsw have been imported to Nabble. Tom you can remove the
mbox files from your server.

Best regards

--
Jorge Sanz
http://es.osgeo.org

Done. Thanks Jorge!

Sent from my iPhone

On 2013-05-27, at 13:09, "Jorge Gaspar Sanz Salinas" <jsanz@osgeo.org> wrote:

On 26 May 2013 20:29, Jorge Gaspar Sanz Salinas <jsanz@osgeo.org> wrote:

On 26 May 2013 20:19, Tom Kralidis <tomkralidis@hotmail.com> wrote:

From: jsanz@osgeo.org
Date: Sun, 26 May 2013 19:54:01 +0200
To: sac@lists.osgeo.org
Subject: Re: [SAC] pycsw-devel mbox file for Nabble setup

Hi sorry for the delay, I was at Geocamp PT in Óbidos :slight_smile:

On 24 May 2013 14:07, Tom Kralidis <tomkralidis@hotmail.com> wrote:

Hi Jorge: thanks for the info. Sure, good idea. What needs to happen for http://pycsw-dev.20702.n7.nabble.com/ to be part of OSGeo Nabble? FYI pycsw is an OSGeo project in incubation, so I'm not sure what the inclusion rules are.

No problem, the only thing to happen is that pcsw project accepts
being archived at OSGeo nabble archive. Being in incubation is indeed
a strong reason.

pycsw accepts being archived in OSGeo nabble archive (per https://github.com/geopython/pycsw/issues/152). Thanks.

FYI, for the mbox file, I was able to find it at http://lists.osgeo.org/mailman/private/pycsw-devel.mbox/pycsw-devel.mbox. However this only includes the last 13 months. Yet the browseable archive (http://lists.osgeo.org/pipermail/pycsw-devel/) has more than that.

Note that we ported the mbox from sf.net to osgeo 13 months ago (see http://trac.osgeo.org/osgeo/ticket/888), so I'm not sure if this is related. Bottom line is that we need a single .mbox for Nabble to import.

Well if we can got both mbox files we can ask Nabble team to import
them, I don't see any problem. We just need to provide them links
where they can grab the files.

Both mbox files can be found in http://kralidis.ca/tmp/k/n.tgz. I will delete this location once imported into Nabble.

As your new archive is almost empty, we can just create a new one
under OSGeo forum and ask for the import at Nabble help forum. I'll do
it right now and will wait for your instructions for the mbox import.

OK, I've deleted the pycsw nabble, so the only pycsw devel on nabble is now at http://osgeo-org.1560.x6.nabble.com/pycsw-devel-f5055821.html -- thanks!!

..Tom

Perfect,

I've asked for the import[1]. I'll notify here as soon as the files
are imported to the Nabble forum.

Cheers!
[1] http://support.nabble.com/mbox-files-import-td7584587.html

Archives of pycsw have been imported to Nabble. Tom you can remove the
mbox files from your server.

Best regards

--
Jorge Sanz
http://es.osgeo.org