Qpidd [System] error Error reading socket:

Hi again,

I spotted something else, my /var/log/messages is filling up with a
continuous stream of these errors:

Feb 16 08:40:04 foremantest qpidd[1053]: 2015-02-16 08:40:04
[System] error Error reading socket: Success(0)
Feb 16 08:40:09 foremantest qpidd: 2015-02-16 08:40:09 [System]
error Error reading socket: Success(0)
Feb 16 08:40:09 foremantest qpidd[1053]: 2015-02-16 08:40:09
[System] error Error reading socket: Success(0)
Feb 16 08:40:14 foremantest qpidd: 2015-02-16 08:40:14 [System]
error Error reading socket: Success(0)
Feb 16 08:40:14 foremantest qpidd[1053]: 2015-02-16 08:40:14
[System] error Error reading socket: Success(0)
Feb 16 08:40:19 foremantest qpidd: 2015-02-16 08:40:19 [System]
error Error reading socket: Success(0)
Feb 16 08:40:19 foremantest qpidd[1053]: 2015-02-16 08:40:19
[System] error Error reading socket: Success(0)
Feb 16 08:40:25 foremantest qpidd: 2015-02-16 08:40:25 [System]
error Error reading socket: Success(0)
Feb 16 08:40:25 foremantest qpidd[1053]: 2015-02-16 08:40:25
[System] error Error reading socket: Success(0)
Feb 16 08:40:30 foremantest qpidd: 2015-02-16 08:40:30 [System]
error Error reading socket: Success(0)
Feb 16 08:40:30 foremantest qpidd[1053]: 2015-02-16 08:40:30
[System] error Error reading socket: Success(0)
Feb 16 08:40:35 foremantest qpidd: 2015-02-16 08:40:35 [System]
error Error reading socket: Success(0)

Any idea of how to get rid of these? Running fresh install of Katello
2.1 with foreman 1.7.2 on Centos 7

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

··· ----------------
Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01

> Hi again,
>
> I spotted something else, my /var/log/messages is filling up with a
> continuous stream of these errors:
>
> Feb 16 08:40:04 foremantest qpidd[1053]: 2015-02-16 08:40:04
> [System] error Error reading socket: Success(0)
> Feb 16 08:40:09 foremantest qpidd: 2015-02-16 08:40:09 [System]
> error Error reading socket: Success(0)
> Feb 16 08:40:09 foremantest qpidd[1053]: 2015-02-16 08:40:09
> [System] error Error reading socket: Success(0)
> Feb 16 08:40:14 foremantest qpidd: 2015-02-16 08:40:14 [System]
> error Error reading socket: Success(0)
> Feb 16 08:40:14 foremantest qpidd[1053]: 2015-02-16 08:40:14
> [System] error Error reading socket: Success(0)
> Feb 16 08:40:19 foremantest qpidd: 2015-02-16 08:40:19 [System]
> error Error reading socket: Success(0)
> Feb 16 08:40:19 foremantest qpidd[1053]: 2015-02-16 08:40:19
> [System] error Error reading socket: Success(0)
> Feb 16 08:40:25 foremantest qpidd: 2015-02-16 08:40:25 [System]
> error Error reading socket: Success(0)
> Feb 16 08:40:25 foremantest qpidd[1053]: 2015-02-16 08:40:25
> [System] error Error reading socket: Success(0)
> Feb 16 08:40:30 foremantest qpidd: 2015-02-16 08:40:30 [System]
> error Error reading socket: Success(0)
> Feb 16 08:40:30 foremantest qpidd[1053]: 2015-02-16 08:40:30
> [System] error Error reading socket: Success(0)
> Feb 16 08:40:35 foremantest qpidd: 2015-02-16 08:40:35 [System]
> error Error reading socket: Success(0)
>
>
> Any idea of how to get rid of these? Running fresh install of Katello
> 2.1 with foreman 1.7.2 on Centos 7

Could it be this? Do you see the corresponding logs in
/var/log/foreman/production.log?

That may explain your other question as well.

http://projects.theforeman.org/issues/9068

··· On Mon, Feb 16, 2015 at 08:49:04AM +0100, Jorick Astrego wrote:

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts


Tel: 053 20 30 270 info@netbulae.eu Staalsteden 4-3A KvK 08198180
Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01



You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Ah yes, thanks!

I see:

step 5115e046-32cd-4e7a-ba4b-1f68502fb658:2 dropping event

Dynflow::Executors::Abstract::Event[execution_plan_id:
5115e046-32cd-4e7a-ba4b-1f68502fb658, step_id: 2, event:
Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message:
Failed to connect (reconnect disabled)], result:
#<Dynflow::Future:0x0000000ad2da48>]
step e7f04d42-51ff-4a48-9746-f6a9f026b1b1:2 dropping event
Dynflow::Executors::Abstract::Event[execution_plan_id:
e7f04d42-51ff-4a48-9746-f6a9f026b1b1, step_id: 2, event:
Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message:
Failed to connect (reconnect disabled)], result:
#<Dynflow::Future:0x0000000f2bfe80>]
step ed89b1a4-9a27-42f4-a7f4-2449416c2a02:2 dropping event
Dynflow::Executors::Abstract::Event[execution_plan_id:
ed89b1a4-9a27-42f4-a7f4-2449416c2a02, step_id: 2, event:
Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message:
Failed to connect (reconnect disabled)], result:
#<Dynflow::Future:0x0000000ee24e48>]
step 00e57fba-05da-469a-926a-c10a31bb8901:2 dropping event
Dynflow::Executors::Abstract::Event[execution_plan_id:
00e57fba-05da-469a-926a-c10a31bb8901, step_id: 2, event:
Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message:
Failed to connect (reconnect disabled)], result:
#<Dynflow::Future:0x0000000ef38370>]

So I guess the only way to fix it for now is redeploy on Centos 6…

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

··· On 02/16/2015 09:00 AM, Stephen Benjamin wrote: > On Mon, Feb 16, 2015 at 08:49:04AM +0100, Jorick Astrego wrote: >> Hi again, >> >> I spotted something else, my /var/log/messages is filling up with a >> continuous stream of these errors: >> >> Feb 16 08:40:04 foremantest qpidd[1053]: 2015-02-16 08:40:04 >> [System] error Error reading socket: Success(0) >> Feb 16 08:40:09 foremantest qpidd: 2015-02-16 08:40:09 [System] >> error Error reading socket: Success(0) >> Feb 16 08:40:09 foremantest qpidd[1053]: 2015-02-16 08:40:09 >> [System] error Error reading socket: Success(0) >> Feb 16 08:40:14 foremantest qpidd: 2015-02-16 08:40:14 [System] >> error Error reading socket: Success(0) >> Feb 16 08:40:14 foremantest qpidd[1053]: 2015-02-16 08:40:14 >> [System] error Error reading socket: Success(0) >> Feb 16 08:40:19 foremantest qpidd: 2015-02-16 08:40:19 [System] >> error Error reading socket: Success(0) >> Feb 16 08:40:19 foremantest qpidd[1053]: 2015-02-16 08:40:19 >> [System] error Error reading socket: Success(0) >> Feb 16 08:40:25 foremantest qpidd: 2015-02-16 08:40:25 [System] >> error Error reading socket: Success(0) >> Feb 16 08:40:25 foremantest qpidd[1053]: 2015-02-16 08:40:25 >> [System] error Error reading socket: Success(0) >> Feb 16 08:40:30 foremantest qpidd: 2015-02-16 08:40:30 [System] >> error Error reading socket: Success(0) >> Feb 16 08:40:30 foremantest qpidd[1053]: 2015-02-16 08:40:30 >> [System] error Error reading socket: Success(0) >> Feb 16 08:40:35 foremantest qpidd: 2015-02-16 08:40:35 [System] >> error Error reading socket: Success(0) >> >> >> Any idea of how to get rid of these? Running fresh install of Katello >> 2.1 with foreman 1.7.2 on Centos 7 > > Could it be this? Do you see the corresponding logs in > /var/log/foreman/production.log? > > That may explain your other question as well. > > http://projects.theforeman.org/issues/9068 > ----------------
Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01

Hi jorick,

Had the same problem on Centos 6.6… Have you successfully deployed on
lower versions of Centos 6?

··· On Monday, February 16, 2015 at 4:59:38 PM UTC+8, Jorick Astrego wrote: > > > On 02/16/2015 09:00 AM, Stephen Benjamin wrote: > > On Mon, Feb 16, 2015 at 08:49:04AM +0100, Jorick Astrego wrote: > >> Hi again, > >> > >> I spotted something else, my /var/log/messages is filling up with a > >> continuous stream of these errors: > >> > >> Feb 16 08:40:04 foremantest qpidd[1053]: 2015-02-16 08:40:04 > >> [System] error Error reading socket: Success(0) > >> Feb 16 08:40:09 foremantest qpidd: 2015-02-16 08:40:09 [System] > >> error Error reading socket: Success(0) > >> Feb 16 08:40:09 foremantest qpidd[1053]: 2015-02-16 08:40:09 > >> [System] error Error reading socket: Success(0) > >> Feb 16 08:40:14 foremantest qpidd: 2015-02-16 08:40:14 [System] > >> error Error reading socket: Success(0) > >> Feb 16 08:40:14 foremantest qpidd[1053]: 2015-02-16 08:40:14 > >> [System] error Error reading socket: Success(0) > >> Feb 16 08:40:19 foremantest qpidd: 2015-02-16 08:40:19 [System] > >> error Error reading socket: Success(0) > >> Feb 16 08:40:19 foremantest qpidd[1053]: 2015-02-16 08:40:19 > >> [System] error Error reading socket: Success(0) > >> Feb 16 08:40:25 foremantest qpidd: 2015-02-16 08:40:25 [System] > >> error Error reading socket: Success(0) > >> Feb 16 08:40:25 foremantest qpidd[1053]: 2015-02-16 08:40:25 > >> [System] error Error reading socket: Success(0) > >> Feb 16 08:40:30 foremantest qpidd: 2015-02-16 08:40:30 [System] > >> error Error reading socket: Success(0) > >> Feb 16 08:40:30 foremantest qpidd[1053]: 2015-02-16 08:40:30 > >> [System] error Error reading socket: Success(0) > >> Feb 16 08:40:35 foremantest qpidd: 2015-02-16 08:40:35 [System] > >> error Error reading socket: Success(0) > >> > >> > >> Any idea of how to get rid of these? Running fresh install of Katello > >> 2.1 with foreman 1.7.2 on Centos 7 > > > > Could it be this? Do you see the corresponding logs in > > /var/log/foreman/production.log? > > > > That may explain your other question as well. > > > > http://projects.theforeman.org/issues/9068 > > > Ah yes, thanks! > > I see: > > step 5115e046-32cd-4e7a-ba4b-1f68502fb658:2 dropping event > Dynflow::Executors::Abstract::Event[execution_plan_id: > 5115e046-32cd-4e7a-ba4b-1f68502fb658, step_id: 2, event: > Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message: Failed > to connect (reconnect disabled)], result: > #] > step e7f04d42-51ff-4a48-9746-f6a9f026b1b1:2 dropping event > Dynflow::Executors::Abstract::Event[execution_plan_id: > e7f04d42-51ff-4a48-9746-f6a9f026b1b1, step_id: 2, event: > Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message: Failed > to connect (reconnect disabled)], result: > #] > step ed89b1a4-9a27-42f4-a7f4-2449416c2a02:2 dropping event > Dynflow::Executors::Abstract::Event[execution_plan_id: > ed89b1a4-9a27-42f4-a7f4-2449416c2a02, step_id: 2, event: > Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message: Failed > to connect (reconnect disabled)], result: > #] > step 00e57fba-05da-469a-926a-c10a31bb8901:2 dropping event > Dynflow::Executors::Abstract::Event[execution_plan_id: > 00e57fba-05da-469a-926a-c10a31bb8901, step_id: 2, event: > Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message: Failed > to connect (reconnect disabled)], result: > #] > > So I guess the only way to fix it for now is redeploy on Centos 6.... > > > > > > > > > Met vriendelijke groet, With kind regards, > > Jorick Astrego > > *Netbulae Virtualization Experts * > ------------------------------ > Tel: 053 20 30 270 in...@netbulae.eu Staalsteden 4-3A KvK > 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW > NL821234584B01 > ------------------------------ > >

> Hi jorick,
>
> Had the same problem on Centos 6.6… Have you successfully deployed
> on lower versions of Centos 6?
>
Nope I do the following after every reboot:

"service tomcat6 restart && service foreman restart"

Don't feel much for downgrading.

Regards,
Jorick

··· On 03/09/2015 07:43 AM, Peter Santiago wrote:

On Monday, February 16, 2015 at 4:59:38 PM UTC+8, Jorick Astrego wrote:

On 02/16/2015 09:00 AM, Stephen Benjamin wrote:
> On Mon, Feb 16, 2015 at 08:49:04AM +0100, Jorick Astrego wrote:
>> Hi again,
>>
>> I spotted something else, my /var/log/messages is filling up with a
>> continuous stream of these errors:
>>
>>     Feb 16 08:40:04 foremantest qpidd[1053]: 2015-02-16 08:40:04
>>     [System] error Error reading socket: Success(0)
>>     Feb 16 08:40:09 foremantest qpidd: 2015-02-16 08:40:09 [System]
>>     error Error reading socket: Success(0)
>>     Feb 16 08:40:09 foremantest qpidd[1053]: 2015-02-16 08:40:09
>>     [System] error Error reading socket: Success(0)
>>     Feb 16 08:40:14 foremantest qpidd: 2015-02-16 08:40:14 [System]
>>     error Error reading socket: Success(0)
>>     Feb 16 08:40:14 foremantest qpidd[1053]: 2015-02-16 08:40:14
>>     [System] error Error reading socket: Success(0)
>>     Feb 16 08:40:19 foremantest qpidd: 2015-02-16 08:40:19 [System]
>>     error Error reading socket: Success(0)
>>     Feb 16 08:40:19 foremantest qpidd[1053]: 2015-02-16 08:40:19
>>     [System] error Error reading socket: Success(0)
>>     Feb 16 08:40:25 foremantest qpidd: 2015-02-16 08:40:25 [System]
>>     error Error reading socket: Success(0)
>>     Feb 16 08:40:25 foremantest qpidd[1053]: 2015-02-16 08:40:25
>>     [System] error Error reading socket: Success(0)
>>     Feb 16 08:40:30 foremantest qpidd: 2015-02-16 08:40:30 [System]
>>     error Error reading socket: Success(0)
>>     Feb 16 08:40:30 foremantest qpidd[1053]: 2015-02-16 08:40:30
>>     [System] error Error reading socket: Success(0)
>>     Feb 16 08:40:35 foremantest qpidd: 2015-02-16 08:40:35 [System]
>>     error Error reading socket: Success(0)
>>
>>
>> Any idea of how to get rid of these? Running fresh install of
Katello
>> 2.1 with foreman 1.7.2 on Centos 7
>
> Could it be this? Do you see the corresponding logs in
> /var/log/foreman/production.log?
>
> That may explain your other question as well.
>
> http://projects.theforeman.org/issues/9068
<http://projects.theforeman.org/issues/9068>
>
Ah yes, thanks!

I see:

    step 5115e046-32cd-4e7a-ba4b-1f68502fb658:2 dropping event
Dynflow::Executors::Abstract::Event[execution_plan_id:
5115e046-32cd-4e7a-ba4b-1f68502fb658, step_id: 2, event:
Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message:
Failed to connect (reconnect disabled)], result:
#<Dynflow::Future:0x0000000ad2da48>]
    step e7f04d42-51ff-4a48-9746-f6a9f026b1b1:2 dropping event
Dynflow::Executors::Abstract::Event[execution_plan_id:
e7f04d42-51ff-4a48-9746-f6a9f026b1b1, step_id: 2, event:
Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message:
Failed to connect (reconnect disabled)], result:
#<Dynflow::Future:0x0000000f2bfe80>]
    step ed89b1a4-9a27-42f4-a7f4-2449416c2a02:2 dropping event
Dynflow::Executors::Abstract::Event[execution_plan_id:
ed89b1a4-9a27-42f4-a7f4-2449416c2a02, step_id: 2, event:
Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message:
Failed to connect (reconnect disabled)], result:
#<Dynflow::Future:0x0000000ee24e48>]
    step 00e57fba-05da-469a-926a-c10a31bb8901:2 dropping event
Dynflow::Executors::Abstract::Event[execution_plan_id:
00e57fba-05da-469a-926a-c10a31bb8901, step_id: 2, event:
Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message:
Failed to connect (reconnect disabled)], result:
#<Dynflow::Future:0x0000000ef38370>]

So I guess the only way to fix it for now is redeploy on Centos 6....








Met vriendelijke groet, With kind regards,

Jorick Astrego*

Netbulae Virtualization Experts *
------------------------------------------------------------------------
Tel: 053 20 30 270 	in...@netbulae.eu <javascript:> 	Staalsteden
4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu <http://www.netbulae.eu> 	7547
TA Enschede 	BTW NL821234584B01


------------------------------------------------------------------------


You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts


Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01

>
>> Hi jorick,
>>
>> Had the same problem on Centos 6.6… Have you successfully deployed
>> on lower versions of Centos 6?
>>
> Nope I do the following after every reboot:
>
> "service tomcat6 restart && service foreman restart"
>
> Don't feel much for downgrading.
>
> Regards,
> Jorick

And sometimes when tasks get stuck it's the same fix, check the
catalina.out log for errors.

Regards,

Jorick
>
>>
>>
>> >> Hi again,
>> >>
>> >> I spotted something else, my /var/log/messages is filling up
>> with a
>> >> continuous stream of these errors:
>> >>
>> >> Feb 16 08:40:04 foremantest qpidd[1053]: 2015-02-16 08:40:04
>> >> [System] error Error reading socket: Success(0)
>> >> Feb 16 08:40:09 foremantest qpidd: 2015-02-16 08:40:09
>> [System]
>> >> error Error reading socket: Success(0)
>> >> Feb 16 08:40:09 foremantest qpidd[1053]: 2015-02-16 08:40:09
>> >> [System] error Error reading socket: Success(0)
>> >> Feb 16 08:40:14 foremantest qpidd: 2015-02-16 08:40:14
>> [System]
>> >> error Error reading socket: Success(0)
>> >> Feb 16 08:40:14 foremantest qpidd[1053]: 2015-02-16 08:40:14
>> >> [System] error Error reading socket: Success(0)
>> >> Feb 16 08:40:19 foremantest qpidd: 2015-02-16 08:40:19
>> [System]
>> >> error Error reading socket: Success(0)
>> >> Feb 16 08:40:19 foremantest qpidd[1053]: 2015-02-16 08:40:19
>> >> [System] error Error reading socket: Success(0)
>> >> Feb 16 08:40:25 foremantest qpidd: 2015-02-16 08:40:25
>> [System]
>> >> error Error reading socket: Success(0)
>> >> Feb 16 08:40:25 foremantest qpidd[1053]: 2015-02-16 08:40:25
>> >> [System] error Error reading socket: Success(0)
>> >> Feb 16 08:40:30 foremantest qpidd: 2015-02-16 08:40:30
>> [System]
>> >> error Error reading socket: Success(0)
>> >> Feb 16 08:40:30 foremantest qpidd[1053]: 2015-02-16 08:40:30
>> >> [System] error Error reading socket: Success(0)
>> >> Feb 16 08:40:35 foremantest qpidd: 2015-02-16 08:40:35
>> [System]
>> >> error Error reading socket: Success(0)
>> >>
>> >>
>> >> Any idea of how to get rid of these? Running fresh install of
>> Katello
>> >> 2.1 with foreman 1.7.2 on Centos 7
>> >
>> > Could it be this? Do you see the corresponding logs in
>> > /var/log/foreman/production.log?
>> >
>> > That may explain your other question as well.
>> >
>> > Bug #9068: foreman-tasks qpid connection seems broken - Katello - Foreman
>> <Bug #9068: foreman-tasks qpid connection seems broken - Katello - Foreman>
>> >
>> Ah yes, thanks!
>>
>> I see:
>>
>> step 5115e046-32cd-4e7a-ba4b-1f68502fb658:2 dropping event
>> Dynflow::Executors::Abstract::Event[execution_plan_id:
>> 5115e046-32cd-4e7a-ba4b-1f68502fb658, step_id: 2, event:
>> Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message: Failed
>> to connect (reconnect disabled)], result:
>> #<Dynflow::Future:0x0000000ad2da48>]
>> step e7f04d42-51ff-4a48-9746-f6a9f026b1b1:2 dropping event
>> Dynflow::Executors::Abstract::Event[execution_plan_id:
>> e7f04d42-51ff-4a48-9746-f6a9f026b1b1, step_id: 2, event:
>> Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message: Failed
>> to connect (reconnect disabled)], result:
>> #<Dynflow::Future:0x0000000f2bfe80>]
>> step ed89b1a4-9a27-42f4-a7f4-2449416c2a02:2 dropping event
>> Dynflow::Executors::Abstract::Event[execution_plan_id:
>> ed89b1a4-9a27-42f4-a7f4-2449416c2a02, step_id: 2, event:
>> Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message: Failed
>> to connect (reconnect disabled)], result:
>> #<Dynflow::Future:0x0000000ee24e48>]
>> step 00e57fba-05da-469a-926a-c10a31bb8901:2 dropping event
>> Dynflow::Executors::Abstract::Event[execution_plan_id:
>> 00e57fba-05da-469a-926a-c10a31bb8901, step_id: 2, event:
>> Actions::Candlepin::ListenOnCandlepinEvents::NotConnected[message: Failed
>> to connect (reconnect disabled)], result:
>> #<Dynflow::Future:0x0000000ef38370>]
>>
>> So I guess the only way to fix it for now is redeploy on Centos 6…
>>
>>
>>
>>
>>
>>
>>
>>
>> Met vriendelijke groet, With kind regards,
>>
>> Jorick Astrego*
>>
>> Netbulae Virtualization Experts *
>> ------------------------------------------------------------------------
>> Tel: 053 20 30 270 in...@netbulae.eu <javascript:> Staalsteden
>> 4-3A KvK 08198180
>> Fax: 053 20 30 271 www.netbulae.eu <http://www.netbulae.eu>
>> 7547 TA Enschede BTW NL821234584B01
>>
>>
>> ------------------------------------------------------------------------
>>
>> –
>> You received this message because you are subscribed to the Google
>> Groups "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to foreman-users+unsubscribe@googlegroups.com
>> <mailto:foreman-users+unsubscribe@googlegroups.com>.
>> To post to this group, send email to foreman-users@googlegroups.com
>> <mailto:foreman-users@googlegroups.com>.
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> Met vriendelijke groet, With kind regards,
>
> Jorick Astrego*
>
> Netbulae Virtualization Experts *
> ------------------------------------------------------------------------
> Tel: 053 20 30 270 info@netbulae.eu Staalsteden 4-3A KvK 08198180
> Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01
>
>
> ------------------------------------------------------------------------
>
> –
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-users+unsubscribe@googlegroups.com
> <mailto:foreman-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to foreman-users@googlegroups.com
> <mailto:foreman-users@googlegroups.com>.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

··· On 03/09/2015 11:13 AM, Jorick Astrego wrote: > On 03/09/2015 07:43 AM, Peter Santiago wrote: >> On Monday, February 16, 2015 at 4:59:38 PM UTC+8, Jorick Astrego wrote: >> On 02/16/2015 09:00 AM, Stephen Benjamin wrote: >> > On Mon, Feb 16, 2015 at 08:49:04AM +0100, Jorick Astrego wrote:
Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01