Pkgrepo fails over HTTP, works on NFS

Hello everyone,
I am trying to set up a local copy of solaris 11 x64 packages, so have downloaded, concatenated and unpacked the repo ISOs in a folder on a Linux box, thinking it would be a simple matter of making the files available under Apache's root. pkgrepo seems to think otherwise though, as it makes a request for a non-existent file then fails:
root@sol11:~# pkgrepo info -s http://linuxbox/pub/sol11/repo/
pkgrepo: http protocol error: code: 404 reason: Not Found
request is for "GET /pub/sol11/repo/versions/0/ HTTP/1.1" which is very much not there.
I did triplecheck the ISOs, no files are missing. Also, when exporting the same folder from linuxbox over NFS:
/repo on linuxbox:/mnt/sol11/repo remote/read/write/setuid/devices/rstchown/xattr/dev=8b00004
pkgrepo info -s /repo/
PUBLISHER PACKAGES STATUS UPDATED
solaris 4292 online 2012-09-04
All is fine, i can install packages etc.
Any clue on what breaks it when specifying a HTTP source?

NM, figured it out. Creating a working repo seems to require a Solaris box, from which I mounted the NFS share of the Linux box, unpacked the ISOs on it, linked the foldr in the webroot, and
pkgrepo create /repo (the NFS mount point)
pkgrecv -s http://pkg.oracle.com/solaris/release/ -d /repo/ '*' (d/l all available updates)
pkgrepo -s /repo refresh
pkg set-publisher -G '*' -M '*' -g http://linuxbox/sol11/repo/ solaris

Similar Messages

How does fail-over database work

Hi,
I have two databases of oracle 10g running on linux and windows. I have to make one of these databasse as a failover database. What is the solution.
Oracle Fail Safe works only in microsft clustered server i.e mostly in windows environments.
What if the both the databases are from different os, then Failsafe doesnt work.
If anyone can suggest me the techonology for this kind of scenario, I would be very thankful.
Regards,
Prabhath

Thanks for the replies. What I have been able to determine from how we run our KKBC_HOE is that we run KKRC just for the current month. Then we run KKBC_HOE for the current month. The KKBC_HOE picks up all activity for the "actual" column that has occurred during that month. But the Target column only get poppulated if the order is marked DLV or TECO.
To measure overall performance you really would need to run this report over several months. Also, does anyone know if the target is taking the standard cost per unit X Planned order quantity or does it take Standard Cost X Actuall Quantity received?
Although there is a Target line based on the actual number of cases received it seems like the rest of the report is based on the Order Planned amount. I'm trying to figure out if we have all our switches set right for this report.
Thanks for your feedback.

FMS4 Sample player RTMP fails but HTTP works

FMS4: localhost or localhost:8134 the same:
For the Stream Video (RTMP) I cannot connect; but using the PLAY VIDEO(HTTP) is fine.
RTMP show: "we are unable to connect to the content you've requested...."
Currently config enabled HTTP Proxy and allow all in/outbound connection in windows 7 firewall.
BTW, this is for the samples; the "dynamic stream" and "interactive" are all fine.
Any idea?
Thanks!

I installed FMS4 on my Windows 7 machine. And for me everything is working fine. Is it like just after completing the installation, when it opens index.html then sample play for rtmp is not working?
Have you tried playing other videos using rtmp?

[solved] Owncloud over SSL: http works, but over https only apache

Hello,
I try to setup owncloud with SSL.
Accessing over http works, but over https, I reach the default apache page instead of the owncloud page.
(I set up SSL according to https://wiki.archlinux.org/index.php/LAMP#SSL )
How could I make the owncloud site available over https?
relevant files:
owncloud.conf:
<IfModule mod_alias.c>
Alias /owncloud /usr/share/webapps/owncloud/
</IfModule>
<Directory /usr/share/webapps/owncloud/>
Options FollowSymlinks
Require all granted
php_admin_value open_basedir "/srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/owncloud/:/etc/webapps/owncloud/:/mt/daten/owncloud/"
</Directory>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot /usr/share/webapps/owncloud
ServerName http://example.com/owncloud
</VirtualHost>
I tried to change 80 to 443, but then, systemctl restart httpd didn't work. (apache failed)
httpd.conf:
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/access_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
# will be interpreted as '/logs/access_log'.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used. If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
ServerRoot "/etc/httpd"
# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
# Mutex default:/run/httpd
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#Listen 12.34.56.78:80
Listen 80
<IfModule mod_ssl.c>
Listen 443
</IfModule>
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_socache_module modules/mod_authn_socache.so
LoadModule authn_core_module modules/mod_authn_core.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
#LoadModule authz_dbd_module modules/mod_authz_dbd.so
LoadModule authz_core_module modules/mod_authz_core.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule access_compat_module modules/mod_access_compat.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_form_module modules/mod_auth_form.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule allowmethods_module modules/mod_allowmethods.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cache_disk_module modules/mod_cache_disk.so
#LoadModule cache_socache_module modules/mod_cache_socache.so
LoadModule socache_shmcb_module modules/mod_socache_shmcb.so
#LoadModule socache_dbm_module modules/mod_socache_dbm.so
#LoadModule socache_memcache_module modules/mod_socache_memcache.so
#LoadModule watchdog_module modules/mod_watchdog.so
#LoadModule macro_module modules/mod_macro.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule echo_module modules/mod_echo.so
#LoadModule buffer_module modules/mod_buffer.so
#LoadModule data_module modules/mod_data.so
#LoadModule ratelimit_module modules/mod_ratelimit.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule request_module modules/mod_request.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
#LoadModule reflector_module modules/mod_reflector.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule sed_module modules/mod_sed.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule deflate_module modules/mod_deflate.so
#LoadModule xml2enc_module modules/mod_xml2enc.so
#LoadModule proxy_html_module modules/mod_proxy_html.so
LoadModule mime_module modules/mod_mime.so
#LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_debug_module modules/mod_log_debug.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule logio_module modules/mod_logio.so
#LoadModule lua_module modules/mod_lua.so
LoadModule env_module modules/mod_env.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
#LoadModule remoteip_module modules/mod_remoteip.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so
LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_express_module modules/mod_proxy_express.so
#LoadModule session_module modules/mod_session.so
#LoadModule session_cookie_module modules/mod_session_cookie.so
#LoadModule session_crypto_module modules/mod_session_crypto.so
#LoadModule session_dbd_module modules/mod_session_dbd.so
LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
#LoadModule slotmem_plain_module modules/mod_slotmem_plain.so
LoadModule ssl_module modules/mod_ssl.so
#LoadModule dialup_module modules/mod_dialup.so
LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
#LoadModule mpm_event_module modules/mod_mpm_event.so
LoadModule mpm_prefork_module modules/mod_mpm_prefork.so
LoadModule unixd_module modules/mod_unixd.so
#LoadModule heartbeat_module modules/mod_heartbeat.so
#LoadModule heartmonitor_module modules/mod_heartmonitor.so
#LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule asis_module modules/mod_asis.so
#LoadModule info_module modules/mod_info.so
#LoadModule suexec_module modules/mod_suexec.so
#LoadModule cgid_module modules/mod_cgid.so
#LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
#LoadModule imagemap_module modules/mod_imagemap.so
#LoadModule actions_module modules/mod_actions.so
#LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
#LoadModule rewrite_module modules/mod_rewrite.so
#own additions:
LoadModule php5_module modules/libphp5.so
<IfModule unixd_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User http
Group http
</IfModule>
# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
#ServerName www.example.com:80
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
<Directory />
Options FollowSymLinks
AllowOverride none
Require all denied
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/srv/http"
<Directory "/srv/http">
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.4/mod/core.html#options
# for more information.
Options Indexes FollowSymLinks
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# AllowOverride FileInfo AuthConfig Limit
AllowOverride None
# Controls who can get stuff from this server.
Require all granted
</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<Files ".ht*">
Require all denied
</Files>
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "/var/log/httpd/error_log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
<IfModule log_config_module>
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
CustomLog "/var/log/httpd/access_log" common
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog "/var/log/httpd/access_log" combined
</IfModule>
<IfModule alias_module>
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
</IfModule>
<IfModule cgid_module>
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#Scriptsock cgisock
</IfModule>
# "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/srv/http/cgi-bin">
AllowOverride None
Options None
Require all granted
</Directory>
<IfModule mime_module>
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
TypesConfig conf/mime.types
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#AddType application/x-gzip .tgz
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi
# For type maps (negotiated resources):
#AddHandler type-map var
# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults: EnableMMAP On, EnableSendfile Off
#EnableMMAP off
#EnableSendfile on
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
Include conf/extra/httpd-mpm.conf
# Multi-language error messages
Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
Include conf/extra/httpd-autoindex.conf
# Language settings
Include conf/extra/httpd-languages.conf
# User home directories
Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
Include conf/extra/httpd-default.conf
# Include owncloud
Include /etc/httpd/conf/extra/owncloud.conf
Include conf/extra/php5_module.conf
# Configure mod_proxy_html to understand HTML4/XHTML1
<IfModule proxy_html_module>
Include conf/extra/proxy-html.conf
</IfModule>
# Secure (SSL/TLS) connections
Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
# uncomment out the below to deal with user agents that deliberately
# violate open standards by misusing DNT (DNT *must* be a specific
# end-user choice)
#<IfModule setenvif_module>
#BrowserMatch "MSIE 10.0;" bad_DNT
#</IfModule>
#<IfModule headers_module>
#RequestHeader unset DNT env=bad_DNT
#</IfModule>
thanks!
Last edited by Carl Karl (2014-05-06 07:40:53)

OK, solved.
What I made wrong:
https://localhost leads to the apache page
https://localhost/owncloud leads to the owncloud page.
(Just as an information if there are other apache noobs like me...)

Which role do I need DFS or File server on fail over cluster server 2012 R2?

what I want to achieve is that I want to share all my user data files in a central location and to be highly available all the time whether it's a general share or folder redirection data. BUT I'm a bit confused; I have fail over cluster set-up
on server 2012, now I would like to add DFS as a role but than we have another role called File server and virtually it does the same thing as DFS? Means it creates a namespace share that can be access even one of the nodes goes down. Now I am thinking is
that DFS does the replication between two physical location but fail over cluster works slightly differently and with file server it pretty much does the same thing except for replicating data from one drive to another. Now what do you suggest I do or
did I get the concept wrong like a noob?

DFS and Failover Clustering for file shares provides a similar end result for file access, but they are significantly different implementations.
Clustering provides high availability to files by presenting shared access to set a files served from a cluster. With 2012 R2 Microsoft added the ability to create a Scale-out File Server that even allows all nodes of the cluster to server access to
the files for a higher level of performance and other great things. Bottom line with Failover Clusters for files is that there is a single copy of the file presented from the cluster.
DFS on the other hand provides high availability to files by presenting multiple copies of the file by making a copy in two or more locations and presenting a naming space that allows access to the file through any of the network paths. DFS works very
well for files that are primarily read-only. When you get into a situation where there is a lot of updating of the shared files, DFS is not a very good solution. There are ways to implement DFS for read/write files, but it generally requires a
good knowledge of how the files are used and how you want to manage them.
The key to answering your question comes in your first sentence "I want to share all my user data files in a central location and to be highly available all the time". My initial reaction to this is that central location means Failover Cluster
- there is only a single copy of the file. However, "all the time" can be compromised by network failures to the central site. Remote sites would not have access if they can't access the central site. DFS provides the ability to
have copies remotely, but then if you allow updating at multiple sites, you have to manage the merging of the changes, among other things.
. : | : . : | : . tim

Streaming video over http

Hello
I need your help to understand how streaming over http works
In our company we have about 600 users who will be able to view streaming video over http hosted in Internet
We have 100 Mbps Internet link . What can we expect to happen in the network when there is contention for resources to access video on our network which delivers best effort service for video
We have enough bandwidth 4 gigs in local area network to core , so there's no real bandwidth cruch
How to differentiate or monitor bandwidth used for http streaming as against http normal traffic
Sent from Cisco Technical Support iPad App

One step closer:
Changed the crossdomain.xml file (more permissive settings).
Changed the encoding on FMLE to vp6. Working somewhat (don't know what I did to make it start streaming through hds).
But at least now I can get the individual streams in the set manifest file to work:
http://localhost/hds-live/livepkgr/_definst_/livevent/livestream1.f4m
http://localhost/hds-live/livepkgr/_definst_/livevent/livestream2.f4m
http://localhost/hds-live/livepkgr/_definst_/livevent/livestream3.f4m
BUT when I try to play the streams through the set manifest file from http://localhost/liveevent.f4m I'm getting the following error:
"The F4m document contains errors URL missing from Media tag." I'll search the forums to see if anyone else has come across this problem.
I used the f4m config tool to make the file. These are the file's contents:
<manifest xmlns="http://ns.adobe.com/f4m/2.0">
<baseURL>http://localhost/hds-live/livepkgr/_definst_/liveevent/</baseURL>
<media href="livestream1.f4m " bitrate="200"/>
<media href="livestream2.f4m " bitrate="500"/>
<media href="livestream3.f4m " bitrate="1000"/>
</manifest>
Thanks

Preview failed because Adobe Muse could not make a connection over HTTP. The most common cause of this is Firewall software which prevents HTTP connections. You may need to change Firewall settings to allow Adobe Muse to make connections.

Preview failed because Adobe Muse could not make a connection over HTTP. The most common cause of this is Firewall software which prevents HTTP connections. You may need to change Firewall settings to allow Adobe Muse to make connections.
no firewall at all, in win 8.1, turned it off for all networks
ftp and publish works just fine

Hi,
Please take a look at this post : Re: Adobe Muse - Preview Failed
Regards,
Aish

Firefox Proxy Fail-over is not working correctly

I am in a corporate environment, where we must use a complex auto-proxy, by configuring an automatic proxy configuration of http://proxyconf/proxy.pac. I am seeing an intermittent failure with Firefox 3.6.13, where the same site will load after a delay in IE (e.g. it works for half an hour, then fails for a while, etc.).
By using Wireshark and tracing the packets, I have identified that a proxy server is intermittently failing, and Firefox is failing to try the second proxy. The auto proxy rule that is being invoked is:
if (!isResolvable(host)) return "PROXY 172.16.39.201:8080; PROXY 10.241.32.28:8080";
The problem is that Firefox is never failing over - it tries the 172 address 6 times in a row, then gives up and displays the "The proxy server is refusing connections" "Firefox is configured to use a proxy server that is refusing connections." "* Check the proxy settings to make sure that they are correct." "* Contact your network administrator to make sure the proxy server is working." error message. It continues with this behavior regardless of how many attempts, reloads, restarts are tried.
IE on the other hand will try and fail with the 172 address, and then start using the 10. address (which works correctly). Several other applications also work correctly, such as IRC clients.
Obviously the corporate proxy that is failing must be fixed, however Firefox is failing to utilitize the 2nd proxy after the first one fails.
Seems like a bug.
Is there some easy way for me to replace the proxy file with my own file? E.g. replace http://http://proxyconf/proxy.pac with file://c:\..., or use some add-on?
It must be an autoproxy script, as there is no single proxy that I can use for all addresses.

You can correct this issue by forcing the file blocklist.xml to update or wait until Firefox updates the file.<br />
That update will remove the severity="0" flags in the file that cause the problem.
See:
* [/questions/832793?page=2#answer-198407]
* http://forums.mozillazine.org/viewtopic.php?p=10899869#p10899869
*[https://bugzilla.mozilla.org/show_bug.cgi?id=663722 Bug 663722] - The blocklist output is including severity="0" where it shouldn't be

Trial SAN Certificate & Outlook Anywhere (RPC over HTTP) test fail

I am testing exchange 2013 where autodiscover pass while performing Outlook Anywhere (RPC over HTTP) connectivity test failed with invalid SSL certifiate . I am only using self certifiate .do any one idea if any CA provding SAN certificate trial basis.
Don't forget to mark helpful or answer
connect me :-
http://in.linkedin.com/in/satya11
http://facebook.com/satya.1000

Hi,
Agree with the above suggestion, ExRCA test cannot pass with self-signed certificate. And to ensure Outlook Anywhere work well , we need to install the self-signed certificate on all clients machines.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

NFS fail-over

Hello all
We are planning to use remote home directories for our non-system user accounts on our Solaris boxes.
We have two servers to use for fail over.
Is it possible to set up NFS to fail over between both servers?
Cheers
--Andreas

If they can't be on the same subnet, then they can't fail each other over directly. You'd have to have client support, and there's no NFS client I'm aware of that will do that on read/write filesystems.
You could make it work if you could force unmount the clients after a server failure, but that would be annoying.
If the servers had a presence on the same subnet, they could each host a virtual IP address that clients would connect to.
Darren

Extension Mobility not working during fail over

Hello All
I am John. I have a cluster that has 2 subscribers and 1 publisher. We are running 8.5.1. Yesterday I had a case where my one subscriber had failed and everything failed over to the other subscriber. Everything but extension mobility seemed to work. I checked all my certs, I checked the services, I checked the url for the services. Everything seemed to check out correctly. The url is pointed to the publisher and the publisher was available.
What i saw during failover:
When the services button was activated I received the requesting notice. after a while the message changed to Host not found. Then the next message was select service.
I did a restart on the extension mobility service with no effect. The other web applications (such as corp directory) all seem to be working correctly. Extension Mobility is the only service I have running.
When the failover ended and my lost subscriber was available, extension mobility and the services started working again.
Any help or ideas would be greatly appreciated.
Thank you
John

Hi John,
As suggested by iptuser55, switch on the EM service on both the nodes. This is the only way failover would work. There are 2 services in CUCM, Extension Mobility and EMApp. The EMApp runs on all the nodes, and its job is to keep a list of the nodes with the EM service activated. When the top node in that list goes down, the EMApp will then point to the next node in the list, which will act as the Failover.
Here's the architecture of the EM service.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/8x/uc8x/cmapps.html#wp1187822

Blazeds 4.0.0.7548 is not working on Websphere over HTTPS protocol

Hi All
Our application is on Blazeds 4.0.0.7548 deployed on websphere 7.0. While this application works fine on HTTP but it doesn't work consistently on HTTPS. It throws following exception
FaultEvent fault=[RPC Fault faultString="error" faultCode="Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP: Failed"] messageId="C6ABB836-C505-CAFC-F114-0006E0E0305F" type="fault" bubbles=false cancelable=true eventPhase=2.
Following is the screeshot
I don't see any exception in the logs as well.
HTTP works fine, i only see this exception on HTTPS.
Regards
Ravi

As I mentioned earlier, we are using MGCP for that particular fax port and the gateway we use as H323.
Even I'm not pretty sure about using mixed protocol, I believe this gateway gonna used to support call center calls. SInce MGCP is easy for configs they might have confiugred only the port as MGCP endpoint.
Now its not working with both the cases, not in mgcp as well as fallback mode. Can you reveiw the debugs and see why I have to remove "modem passthrough" command from voice service voip section which of our standard config and works well with all other gateway of ours. Please help here.

MAPI over HTTP not working correctly, Outlook 2013 clients prompting for credentials during profile creation or opening depending on security of virtual directory

ENVIRONMENT
-1 Exchange 2013 SP1 CU7 server with all roles that is also a hybrid server with Office 365 tenant, mailboxes are all on premise only LYNC online is being utilized right now.
-Exchange 2013 public folders
-Mix of Outlook 2013 SP1 and Outlook 2010 SP3 clients all fully update to day as of Feb 2015
Outlook anywhere is working perfectly across all clients both internally and externally using autodiscover. Both Outlook 2013 and 2010 clients can open the program and create a profile automatically via autodiscover and no additional logon prompts
are seen.
We set the internal and external mapi virtual directory URLs to a valid URL that also matches the Exchange 2013 SSL certificate. We set the security to ntlm, negotiate on the mapi virtual directory. We reset IIS and enabled mapi over http in
the org config. We run in to problems here.
Outlook 2010 clients appear to be working fine. We can create a new profile and open and close Outlook without any logon prompts and verify that MAPIHTTP and Negotiate are used to connect to Exchange.
Outlook 2013 clients are having problems. As soon as we try to create a profile it says your administrator has made a change that requires you to restart outlook and then a windows logon prompt appears. If we authenticate Outlook will open and connect.
This logon prompt should not occur. We can confirm that it is connecting via MAPI HTTP and Negotiate.
If we set the mapi virtual directory to NTLM only then a logon prompt also appears during every open of Outlook 2013. We can confirm that it is trying to connect with MAPIHTTP via NTLM in the outlook connection test screen.
I do not understand this behavior by Outlook 2013 which was supposed to be designed with MAPI HTTP in mind. I would think the same issues would occur with Outlook 2010 but they do not. I am not sure how to resolve this and I am looking for help.

I have the same problem. Exchange and Outlook are both up to date. After creating a new profile Outlook prompts for username/password. A lot of users also get this prompt while
working - the profiles have been "migrated" from Exchange server 2010. <o:p></o:p>
Niko, as i can see in your screenshot you do not have Mapi over HTTP enabled. Why? You can change settings in the security tab – if you have Mapi over
HTTP enabled all options are grayed out (please correct me if I
am wrong):
This is a very annoying thing – does anybody else have the same problem?
Any suggestions on this?
Marc

Http tunneling (t3 over http) doesn't work!! (examples too)

Hi,
I'm trying to get http tunneling (t3 connection over http protocol) to work. I
ran some examples included with Weblogic that try establishing that connection
(PingTest, HelloApplet, SimpleT3Client), as well as my own test program, and they
all give an error similar to this :
Couldn't get a reference to server. Exception :
javax.naming.CommunicationException. Root exception is java.net.ConnectException:
No server found at HTTP://<IP>:<port>
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:161) at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:200)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java,
Compiled Code) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671) at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242) at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.<init>(InitialContext.java:194)
(I replaced the actual Ip and port with <IP> and <port>).
Now, the server is started and working at that ip and port - it services web http
requests correctly, etc. Regular T3 connection (not over http) also works with
it.
Does anyone know the reason for this problem and/or how to fix it?
Thanks, Leonid Portnoy

It appears that one has to use the "Java Plugin" for this mode to work. The
question is does the version of plugin need to be "in sync" with the JVM
version on the server. ?.
/rk
"Adomas Svirskas" <[email protected]> wrote in message
news:[email protected]...
>
It seems that the solution is to have these two lines in the
properties file:
weblogic.httpd.enable=true
weblogic.httpd.tunnelingenabled=true
Now it works.
Thanks,
Adomas
"Adomas Svirskas" <[email protected]> wrote:
Hi Leonid,
Have you found a solution for this? I have these problems too.
Thanks,
Adomas
"Leonid Portnoy" <[email protected]> wrote:
Hi,
I'm trying to get http tunneling (t3 connection over http protocol)to
work. I
ran some examples included with Weblogic that try establishing thatconnection
(PingTest, HelloApplet, SimpleT3Client), as well as my own test program,
and they
all give an error similar to this :
Couldn't get a reference to server. Exception :
javax.naming.CommunicationException. Root exception is
java.net.ConnectException:
No server found at HTTP://<IP>:<port>
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:161) atweblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:200)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java,
Compiled Code) atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:148)
atweblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:123)
atjavax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.<init>(InitialContext.java:194)
(I replaced the actual Ip and port with <IP> and <port>).
Now, the server is started and working at that ip and port - it services
web http
requests correctly, etc. Regular T3 connection (not over http) alsoworks
with
it.
Does anyone know the reason for this problem and/or how to fix it?
Thanks, Leonid Portnoy

Webdynpro ABAP called from IView JAVA works over http but doesn't over http

Hello gurus, like I said in the subject, we have integrated inside our JAVA portal a WebDynpro ABAP and it's working good over http protocol (http://<servername>:<http_port>/irj/portal), but when you browse the portal over https protocol (https://<servername>:<https_port>/irj/portal), everything works fine exept the WebDynpro ABAP, is like if the javascript components didn't be loaded completly, because the buttons doesn't make anything, and only half of the table that is supossed to be loaded is showed.
Do you know what kind of configuration I'm missing?
Thanks and best regards

You have to note here that for webdynpro ABAP applications, the http/https request is actually served by the backend server.
So, while accessing your webdynpro ABAP application, the request will be like:
https://<mybackendserver>:<backendport>/bc/sap/.....
While creating a system object in your portal (System landscape), you will need to adjust the protocol to https and also set the appropriate https port of the backend server. Also, HTTPS/SSL communication should be enabled on your backend server.
Please check the definition of your system object.
You can find more information by turning on a HTTP trace and checking how the request is routed to the backend server upon accessing the WD4A application.
Thanks,
Shanti

Pkgrepo fails over HTTP, works on NFS

Similar Messages

Maybe you are looking for