Re: monitoring ruby app memory usage with passenger-recycler (was: Cannot require library for passenger in ruby)

2018-02-21 Thread Karli Sjöberg via freebsd-ports 
On Tue, 2018-02-20 at 21:31 +, Marcin Cieslak wrote:
> On Mon, 19 Feb 2018, Karli Sjöberg wrote:
> 
> > > What is the tool you are trying to deploy? foreman_maintain?
> 
> Sorry, I was too quick. This foreman_main is used to download/update
> foreman
> from RedHat Satellite servers, which is not what you want.

Well, I want the "foreman_maintain" package, which includes "passenger-
recycler", so I guess I do want it :)

> 
> However, the passenger-recycler script is a standalone script which
> could possibly used with this little fix:

Ooh, awesome! Yeah, should´ve figured since it´s only at 0.1.3 :)

> 
> https://github.com/theforeman/foreman_maintain/pull/143
> 
> To apply this, please add files/patch-bin_passenger-recycler in the
> port I've sent before:
> 
> --- bin/passenger-recycler.orig 2018-02-20 21:09:18 UTC
> +++ bin/passenger-recycler
> @@ -41,10 +41,10 @@ def process_status?(pid)
>  end
>  
>  require 'phusion_passenger'
> +PhusionPassenger.locate_directories
>  require 'phusion_passenger/platform_info'
>  require 'phusion_passenger/platform_info/ruby'
>  require 'phusion_passenger/admin_tools/memory_stats'
> -PhusionPassenger.locate_directories
>  stats = PhusionPassenger::AdminTools::MemoryStats.new
>  unless stats.platform_provides_private_dirty_rss_information?
>puts 'Please run as root or platform unsupported'

Yes, this works, thanks!

> 
> 
> But the real problem is that Passenger does think it supports
> getting process private dirty RSS memory information only on Linux:
> 
> https://github.com/phusion/passenger/blob/219ad24159ae4033a342e6ad753
> cfee05d98bae0/src/ruby_supportlib/phusion_passenger/admin_tools/memor
> y_stats.rb#L121
> 
> In file
> src/ruby_supportlib/phusion_passenger/admin_tools/memory_stats.rb:
> 
> 120   def platform_provides_private_dirty_rss_information?
> 121 return os_name_simple == "linux"
> 122   end
> 
> This support probably would need to be written. So, unfortunately,
> passenger-recycler
> as written will exit with:
> 
>   Please run as root or platform unsupported

Yes, I have now gotten to this stage at least, thank you very much! I
don´t mind having a look at it, it might be simplest thing to write, or
it´s hell, but I´ll have a look!

Thank you for pointing me in the right direction!

/K

> 
> But passenger-recycler does something very simple - if the amount of
> "private resident RSS
> memory" is higher than specified amount in the configuration file, it
> kills the process.
> 
> You might get a much better monitoring on FreeBSD by monitoring the
> output of
> 
> procstat -v 
> 
> which will give you details about the memory usage of the process and
> see how it is growing
> over time. Maybe you can pinpoint the shared library that causes
> this, if you are lucky.
> 
> Marcin

signature.asc
Description: This is a digitally signed message part

Re: Dropping maintainership for pydio / softether / wmconfig

2018-02-21 Thread Koichiro IWAO 


I'll take the maintainership if nobody wants however
I think security/softether and security/softether-devel
should be maintained by the same maintainer.

Sato-san, would you like to maintain net/softether as well?

2018-02-22 05:50 に Tobias Kortkamp さんは書きました:

On Wed, Feb 21, 2018, at 21:23, n...@arrishq.net wrote:

Hello,

I've stopped using FreeBSD (and now enjoy meltdown and spectre patches
in time) and would - of course - like to drop maintainership for:

security/softether
www/pydio
x11-wm/wmconfig


Done.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to 
"freebsd-ports-unsubscr...@freebsd.org"


--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Dropping maintainership for pydio / softether / wmconfig

2018-02-21 Thread Tobias Kortkamp 
On Wed, Feb 21, 2018, at 21:23, n...@arrishq.net wrote:
> Hello,
> 
> I've stopped using FreeBSD (and now enjoy meltdown and spectre patches 
> in time) and would - of course - like to drop maintainership for:
> 
> security/softether
> www/pydio
> x11-wm/wmconfig

Done.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

RE: FreeBSD Port: icingaweb2-module-director-1.4.3

2018-02-21 Thread Brandon McCorkle 
Thank you Lars,

Please let me know.   I even tried downloading the module from github 
and dropping in the modules directory but receiving the same error.   I'm kind 
of lost what it could be.

-Original Message-
From: Lars Engels [mailto:lars.eng...@0x20.net] 
Sent: Wednesday, February 21, 2018 2:27 PM
To: Brandon McCorkle 
Cc: po...@freebsd.org
Subject: Re: FreeBSD Port: icingaweb2-module-director-1.4.3

On Wed, Feb 21, 2018 at 01:54:54PM +, Brandon McCorkle wrote:
> Hello,
> 
> I was wondering if you've come across this error in your testing I entered on 
> github?
> 
> https://github.com/Icinga/icingaweb2-module-director/issues/1400

Hi Brandon,

I've not seen this error yet, but I'm about to build a new Icinga 2 server 
including Web and Director, so I can take a look if I also encounter the error.

Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: icingaweb2-module-director-1.4.3

2018-02-21 Thread Lars Engels 
On Wed, Feb 21, 2018 at 01:54:54PM +, Brandon McCorkle wrote:
> Hello,
> 
> I was wondering if you've come across this error in your testing I entered on 
> github?
> 
> https://github.com/Icinga/icingaweb2-module-director/issues/1400

Hi Brandon,

I've not seen this error yet, but I'm about to build a new Icinga 2
server including Web and Director, so I can take a look if I also
encounter the error.

Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Dropping maintainership for pydio / softether / wmconfig

2018-02-21 Thread net 

Hello,

I've stopped using FreeBSD (and now enjoy meltdown and spectre patches 
in time) and would - of course - like to drop maintainership for:


security/softether
www/pydio
x11-wm/wmconfig

Additionally I've ports for the Atlassian crowd (Jira, Confluence, 
Bitbucket, Bamboo, Bamboo Build Agent) and these might easily be adopted 
for the rest of Atlassian's software, though using this commercial 
software on FreeBSD might not make much sense because Atlassian won't 
provide any support, even with a valid unlimited users enterprise license. 
So these haven't been submitted yet.


If someone wishes to maintain one of these ports, please drop me a note - 
virtual hugs won't be considered as offensive btw.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for help: www/nginx and 3rd party module

2018-02-21 Thread Matt Smith 

On Feb 21 17:18, Jochen Neumeister wrote:


Which 3rd party modules do you use, which the port itself provides?



This type of thing may be better suited for an online webpage type 
survey rather than potentially getting lots of posts to the mailing list 
with similar things?


I always use and would greatly miss HTTP_DAV_EXT. Because for some 
inexplicable reason they won't put this functionality in the core DAV.


I've also used HTTP_GEOIP2 in the past for a couple of things, but I 
wouldn't miss this one quite as much now.


--
Matt
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Call for help: www/nginx and 3rd party module

2018-02-21 Thread Jochen Neumeister 
The port has grown a lot over the years on 3rd party modules, i'd like 
to open a survey to figure out what modules are actually widely used.


The background of the survey is to find out which 3rd party modules are 
used a lot, and which ones are very little or not at all anymore.


This should help me to remove 3rd party modules, which are not used at 
all (anymore), from the port, because the port has become too big by 
now, as far as the 3rd party modules are concerned.


Which 3rd party modules do you use, which the port itself provides?

Thanks for your help.

Best regards
joneum

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD Port: icingaweb2-module-director-1.4.3

2018-02-21 Thread Brandon McCorkle 
Hello,

I was wondering if you've come across this error in your testing I entered on 
github?

https://github.com/Icinga/icingaweb2-module-director/issues/1400



Brandon McCorkle
Network Administrator
Department of Technology


[Arch Email]
City of Gahanna

200 S. Hamilton Rd.
Gahanna, Ohio 43230
614.342.4071
614.342.4171 (fax)
brandon.mccor...@gahanna.gov

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

2018-02-21 Thread portscout 
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
devel/lua-posix | 34.0.1  | v34.0.4
+-+
net/anet| 0.3.4   | 0.4.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Cannot require library for passenger in ruby

2018-02-21 Thread Karli Sjöberg via freebsd-ports 
On Tue, 2018-02-20 at 20:26 +, Marcin Cieslak wrote:
> On Mon, 19 Feb 2018, Karli Sjöberg wrote:
> 
> > > What is the tool you are trying to deploy? foreman_maintain?
> 
> Can you try the port below? Unfortunately I do not see how
> foreman_maintain may fix your passenger
> installation issues, but here it is:

No, you´re right, it didn´t fix the issue:
# /usr/local/bin/passenger-recycler 
/usr/local/lib/ruby/gems/2.4/gems/foreman_maintain-0.1.3/bin/passenger-recycler:10:
 warning: already initialized constant CONFIG
/usr/local/lib/ruby/gems/2.4/gems/foreman_maintain-0.1.3/bin/passenger-recycler:8:
 warning: previous definition of CONFIG was here
/usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.rb:135:in 
`require': cannot load such file -- /phusion_passenger/utils/tmpio (LoadError)
from 
/usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.rb:135:in 
`rescue in require'
from 
/usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.rb:39:in 
`require'
from 
/usr/local/lib/ruby/gems/2.4/gems/passenger-5.1.12/src/ruby_supportlib/phusion_passenger.rb:240:in
 `require_passenger_lib'
from 
/usr/local/lib/ruby/gems/2.4/gems/passenger-5.1.12/src/ruby_supportlib/phusion_passenger/platform_info.rb:26:in
 `'
from 
/usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.rb:70:in 
`require'
from 
/usr/local/lib/ruby/site_ruby/2.4/rubygems/core_ext/kernel_require.rb:70:in 
`require'
from 
/usr/local/lib/ruby/gems/2.4/gems/foreman_maintain-0.1.3/bin/passenger-recycler:44:in
 `'
from /usr/local/bin/passenger-recycler:23:in `load'
from /usr/local/bin/passenger-recycler:23:in `'

But the port worked, so good job on that! :)

I get the feeling that the installed binaries are fine, it´s
something else, something more basic with passenger, since it bombs at
just trying to load a library that is included directly in the rubygem-
passenger package.

Does anyone have a clue here?

/K

> 
> # This is a shell archive.  Save it in a file, remove anything before
> # this line, and then unpack it by entering "sh file".  Note, it may
> # create directories; files and directories will be owned by you and
> # have default permissions.
> #
> # This archive contains:
> #
> # rubygem-foreman_maintain
> # rubygem-foreman_maintain/Makefile
> # rubygem-foreman_maintain/distinfo
> # rubygem-foreman_maintain/pkg-descr
> #
> echo c - rubygem-foreman_maintain
> mkdir -p rubygem-foreman_maintain > /dev/null 2>&1
> echo x - rubygem-foreman_maintain/Makefile
> sed 's/^X//' >rubygem-foreman_maintain/Makefile <<
> '15090155e0ad279a3a88902efd75aea3'
> X# $FreeBSD: head/devel/rubygem-foreman/Makefile 448125 2017-08-17
> 15:05:14Z sunpoet $
> X
> XPORTNAME=foreman_maintain
> XPORTVERSION= 0.1.3
> XCATEGORIES=  devel rubygems
> XMASTER_SITES=RG
> X
> XMAINTAINER=  r...@freebsd.org
> XCOMMENT= Facility to keep Foreman/Satellite services running
> X
> XRUN_DEPENDS= rubygem-clamp>0:devel/rubygem-clamp \
> X rubygem-highline>0:devel/rubygem-highline \
> X rubocop:devel/rubygem-rubocop \
> X pry:devel/rubygem-pry
> X
> XNO_ARCH= yes
> XUSES=gem shebangfix
> XUSE_RUBY=yes
> X
> XPLIST_FILES= bin/foreman-maintain bin/passenger-recycler
> X
> XSHEBANG_FILES=   ${PLIST_FILES}
> X
> X.include 
> 15090155e0ad279a3a88902efd75aea3
> echo x - rubygem-foreman_maintain/distinfo
> sed 's/^X//' >rubygem-foreman_maintain/distinfo <<
> 'b2bf4dcb1a0a898485a2b273846fd43e'
> XTIMESTAMP = 1519156673
> XSHA256 (rubygem/foreman_maintain-0.1.3.gem) =
> 35f10c7df685072de50f515bfe5c694791d01f5d2eb2ef02c32b693f7e68f73b
> XSIZE (rubygem/foreman_maintain-0.1.3.gem) = 58880
> b2bf4dcb1a0a898485a2b273846fd43e
> echo x - rubygem-foreman_maintain/pkg-descr
> sed 's/^X//' >rubygem-foreman_maintain/pkg-descr <<
> '9944d73c5ee733bda3fa3a0bea6fbf70'
> XA maintenance tool for Foreman/Satellite Ruby applications
> X
> XWWW: https://github.com/theforeman/foreman_maintain
> 9944d73c5ee733bda3fa3a0bea6fbf70
> exit

signature.asc
Description: This is a digitally signed message part

Re: pkg fallout - wrong shared lib version?

2018-02-21 Thread Tijl Coosemans 
On Tue, 20 Feb 2018 18:13:07 -0500 "Jason E. Hale"  wrote:
> On Tue, Feb 20, 2018 at 12:36 PM, Anton Shterenlikht  wrote:
>> My port lang/opencoarrays gives this error
>> via pkg-fallout:
>>
>> ...
>> -- Installing: 
>> /wrkdirs/usr/ports/lang/opencoarrays/work/stage/usr/local/lib/libcaf_mpi.so.1
>> ...
>>  
>> ===>  Building package for opencoarrays-1.9.3  
>> pkg-static: Unable to access file 
>> /wrkdirs/usr/ports/lang/opencoarrays/work/stage/usr/local/lib/libcaf_mpi.so.2:No
>>  such file or directory
>>
>> On the system where I did the testing I get:
>>
>> # pkg info -xl opencoarr
>> opencoarrays-1.9.3:
>> ...
>> /usr/local/lib/libcaf_mpi.so.2
>>
>> Accrdingly I put
>>
>> lib/libcaf_mpi.so.2
>>
>> in pkg-plist
>>
>> Where did I go wrong?
> 
> I just took a quick look at the port and src/mpi/CMakeLists.txt is
> setting the SOVERSION differently depending on which version the
> Fortran compiler is:
> 
> set(CAF_SO_VERSION 0)
> if(gfortran_compiler)
>   if(NOT CMAKE_Fortran_COMPILER_VERSION VERSION_LESS 7.0.0)
> set(CAF_SO_VERSION 2)
>   elseif(NOT CMAKE_Fortran_COMPILER_VERSION VERSION_LESS 6.0.0)
> set(CAF_SO_VERSION 1)
>   endif()
> endif()
> 
> You will probably have to do a check for the compiler version and
> adjust pkg-plist accordingly.
> 
> I've CC'd tijl since he landed this.

Should be fixed in r462483.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"