Can you give more information and description about the output error?  Any
log or anything for a review?

Thanks
El 26/09/2014 19:40, "Justin Bennett" <jbenn...@msjc.edu> escribió:

>  Just an FYI
>
>
>
> I tried the 3.05 iso in Hyper-V 2012, and the Hyper-V Integration modules
> would not install with the usual - apt-get install debian-archive-keyring;
> aptitude update; aptitude upgrade - that I did with 3.03.
>
>
>
> I was able to get 3.03 iso on Hyper-V 2012 and did the mentioned commands
> to update Zen to 3.05 and Hyper-V Integration modules with no issues.
>
>
>
> Thank you all for your support and all you do!
>
>
>
> *Justin Bennett*
>
> Supervisor of Network Technology
> Information Technology
> jbenn...@msjc.edu
>
>
>
> Mt. San Jacinto College
> Phone 951-639-5090
> http://www.msjc.edu
>
>
>
> *d** Security Notice:* MSJC Information Technology Staff will never ask
> for your password. Keep your passwords private to protect yourself and the
> security of our network.
>
>
>
> *From:* Emilio Campos [mailto:emilio.campos.mar...@gmail.com]
> *Sent:* Wednesday, August 27, 2014 5:04 AM
> *To:* zenloadbalancer-support@lists.sourceforge.net
> *Subject:* Re: [Zenloadbalancer-support] [ANNOUNCE] Zen Load Balancer
> 3.05 Community Edition is released
>
>
>
> Hello guys,  Zen load balancer iso has been already updated in Sourceforge.
>
> Thanks and regards!
>
>
>
> 2014-08-27 10:39 GMT+02:00 Laura García Liébana <laur...@sofintel.net>:
>
>  Thank you for your report, it will be reviewed as soon as possible.
>
>
>
> 2014-08-27 9:28 GMT+02:00 Hoffmann Christian <
> christian.hoffm...@hch-net.at>:
>
>   Sorry, I attached a screenshot of the farm-configuration which did not
> show within the mail:
>
> Setting for the farm are:
>
> Type: l4xnat
>
> Protocol Type: ALL
>
> NAT-Type: DNAT
>
> LoadBalanceAlgorithm: Weight connection linear dispatching..
>
> Persistence mode: IPPersistence
>
> Source IP Address Persistence time to limit: 120
>
> Use FarmGuardian to check Backend Servers: active
>
> Check every 5 Sec.
>
> Command to check check_tcp -H HOST -p 5061
>
> IP: x.x.x.x Ports: *
>
>
>
>
>   ------------------------------
>
> *Von:* Hoffmann Christian <christian.hoffm...@hch-net.at>
> *Gesendet:* Mittwoch, 27. August 2014 08:53
> *An:* zenloadbalancer-support@lists.sourceforge.net
> *Betreff:* Re: [Zenloadbalancer-support] [ANNOUNCE] Zen Load Balancer
> 3.05 Community Edition is released
>
>
>
> I installed the new version today...
>
> I have configured a l4xnat farm using the following settings:
>
>  The farm is working fine, but nether the farm, nor the real server
> status is showing any connections.
>
> When I change the farm protocol type to tcp the connections are showing up.
>
>
>
> Is this a known issue?
>
> Should I create 2 farms one for TCP and one for UDP for beeing able to see
> the connections?
>
>
>
> best regards
>
>
>
> Chris
>
>
>   ------------------------------
>
> *Von:* Emilio Campos <emilio.campos.mar...@gmail.com>
> *Gesendet:* Dienstag, 26. August 2014 18:56
> *An:* zenloadbalancer-support@lists.sourceforge.net
> *Betreff:* [Zenloadbalancer-support] [ANNOUNCE] Zen Load Balancer 3.05
> Community Edition is released
>
>
>
> Hi Zen Masters, we announce the last ZLB stable version release which
> includes:
>
> *New Features:*
> [farms] L4 SIP load balancing support
> [farms] Simple GSLB load balancing support
> [ssl] Granted CA SSL Certificates automatic generation
> [gui] Dynamic news platform support
> *Improvements:*
> [gui] HTTP farm client request timeout with unit “seconds”
> [gui] Refreshing timeout for farms status view
> [cluster] Improved RSA synchronization
> [gui] Advise message regarding no cluster configuration found
> [gui] return back button to All Farms in farm edition panel
> *Bugfixes:*
> [farms] Datalink farm wrong info in farms table
> [farms] FG backend status file mutex implementation
> [gui] date-time wrong formatted fix
> [farms] Modification of Priority and Timeout parameters could cause a
> inconsistency in the HTTP/S farms configuration file
> [farms] Farmguardian error in TCP farms, the backends are not remaining
> down while FG is checking them.
>
>   Additionally it includes all changes of 3.04:
>
> *Improvements:*
> [cluster] Cluster service avoid hardcoded vhid and deadratio parameters
> [installation] Postinstallation script global.conf checking
> *Bug fixes:*
> [farmguardian] Farmguardian startup bug fixes
> [farmguardian] Fix FarmGuardian execution for L4 farms
> [farms] Datalink infinite loop getDevData() showing farm info
> [farms] Manage HTTP/S farms connection bug due to wrong lb core child pid
> [farms] L4 persistency multiprotocol command fix
> [farms] Set priority value for L4 by default
> [farmguardian] Farmguardian startup status fixed
> [farms] Farms name hyphens filtering fixed
> [farmguardian] FarmGuardian up status for the backends before stopping the
> FG service
> [farms] L4 netstat connections
> [farms] HTTP/S farm redirect fix when a redirect name is used
> [logs] Regression: delete debug messages
> [farms] Backend states on HTTP/HTTPS farms become inconsistent when
> the service doesn’t exist in the configuration file (the farm restart has
> not been performed). Service ID will be null
> [farms] New backends are not included in the backend status file
> [farms] Setting L4 TTL field is not applied by default. An automatic
> restart is needed
> [farms] DateTime errors in the log files. The DateTime has been
> changed to system ‘date’ command
> [farms] Force drain sessions automatically when a backend is detected as
> down
> [farms] L4 farms connections accounting are not showing properly in the
> status panel
> [config] Delete generated global.conf, it could be rewritten an already
> configured load balancer by the default one
> [installation] Include interactive mode post-installation and error solved
> [installation] Delete config files at installation time
> [gui] Shell error solved getting ZLB version
> [farmguardian] Farmguardian defunct processes and tcp/udp farm malfunction
> [farms] TCP and UDP with pen LB, the backend never comes alive from
> FGdown. These kind of farms doesn’t need to detect the state change for a
> backend, as they need to refresh always the blacklisted timeout
>
>
>
> At this moment it only can be updated via apt, for this, ensure that your
> current /etc/apt/sources.list file is configured as follows:
>
> deb http://ftp.debian.org/debian/ squeeze main non-free
> deb-src http://ftp.debian.org/debian/ squeeze main non-free
> deb http://security.debian.org/ squeeze/updates main
> deb-src http://security.debian.org/ squeeze/updates main
> #official repository for Zen Load Balancer Updates
> deb http://zenloadbalancer.sourceforge.net/apt/x86 v3/
>
> Finally in command line execute the next commands:
>
> apt-get update
> apt-get install zenloadbalancer
>
>
>
>
> It's pending:
>
> Build the Zen Load Balancer 3.05 ISO
>
> Update de doc.
>
> We hope you enjoy the zen experience!
>
>
> --
> Load balancer distribution - Open Source Project
> http://www.zenloadbalancer.com
> Distribution list (subscribe):
> zenloadbalancer-support@lists.sourceforge.net
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
>
>
> --
> Laura García Liébana
> skype id: lauragl82
> gtalk id: laur...@sofintel.net
> email: laur...@sofintel.net
> www.sofintel.net
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
>
>
> --
> Load balancer distribution - Open Source Project
> http://www.zenloadbalancer.com
> Distribution list (subscribe):
> zenloadbalancer-support@lists.sourceforge.net
>
> *WARNING*
>  ------------------------------
>
> This email did not originate from the Mt. San Jacinto College network and
> should be viewed with caution. Please note that computer viruses and
> phishing attempts can be transmitted via email. E-mail transmission cannot
> be guaranteed to be secure or error-free as information could be
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> contain viruses.
>
> If you have any questions or concerns about this email, please contact the
> MSJC Information Technology helpdesk at helpd...@msjc.edu or (951)
> 639-5344.
>
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Zenloadbalancer-support mailing list
Zenloadbalancer-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support

Reply via email to