When I use Mailman and ExIM4 to set up a mailing list server, I send information to the mailing list using my personal mailbox, and the message "Action: failed, Final-Recipient: rfc822; dev#tomtoworld.xyz Status: 5.0.0" is returned. The log output is as follows:
2022-05-04 13:19:09 1nmEuL-0000Ht-G3 <= 353712217#qq.com H=(71b59c6d89cc) [43.155.80.72] P=esmtp S=19481 id=tencent_42C7156C70D41B29B12B9B720262AA270908#qq.com T="test" from <353712217#qq.
2022-05-04 13:19:09 1nmEuL-0000Hp-F0 => dev#tomtoworld.xyz F=<353712217#qq.com> P=<353712217#qq.com> R=dnslookup_relay_to_domains T=remote_smtp H=tomtoworld.xyz [43.155.80.72] C="250 OK id
2022-05-04 13:19:09 1nmEuL-0000Hp-F0 Completed
2022-05-04 13:19:09 1nmEuL-0000Hx-HB <= 353712217#qq.com H=(71b59c6d89cc) [43.155.80.72] P=esmtp S=20101 id=tencent_42C7156C70D41B29B12B9B720262AA270908#qq.com T="test" from <353712217#qq.
2022-05-04 13:19:09 1nmEuL-0000Ht-G3 => dev#tomtoworld.xyz F=<353712217#qq.com> P=<353712217#qq.com> R=dnslookup_relay_to_domains T=remote_smtp H=tomtoworld.xyz [43.155.80.72] C="250 OK id
2022-05-04 13:19:09 1nmEuL-0000Ht-G3 Completed
2022-05-04 13:19:09 1nmEuL-0000I1-IH <= 353712217#qq.com H=(71b59c6d89cc) [43.155.80.72] P=esmtp S=20721 id=tencent_42C7156C70D41B29B12B9B720262AA270908#qq.com T="test" from <353712217#qq.
2022-05-04 13:19:09 1nmEuL-0000Hx-HB => dev#tomtoworld.xyz F=<353712217#qq.com> P=<353712217#qq.com> R=dnslookup_relay_to_domains T=remote_smtp H=tomtoworld.xyz [43.155.80.72] C="250 OK id
2022-05-04 13:19:09 1nmEuL-0000Hx-HB Completed
2022-05-04 13:19:09 1nmEuL-0000I5-JM <= 353712217#qq.com H=(71b59c6d89cc) [43.155.80.72] P=esmtp S=21341 id=tencent_42C7156C70D41B29B12B9B720262AA270908#qq.com T="test" from <353712217#qq.
2022-05-04 13:19:09 1nmEuL-0000I1-IH => dev#tomtoworld.xyz F=<353712217#qq.com> P=<353712217#qq.com> R=dnslookup_relay_to_domains T=remote_smtp H=tomtoworld.xyz [43.155.80.72] C="250 OK id
2022-05-04 13:19:09 1nmEuL-0000I1-IH Completed
2022-05-04 13:19:09 1nmEuL-0000I5-JM ** dev#tomtoworld.xyz F=<353712217#qq.com>: Too many "Received" headers - suspected mail loop
2022-05-04 13:19:09 1nmEuL-0000I8-KE <= <> R=1nmEuL-0000I5-JM U=Debian-exim P=local S=22506 T="Mail delivery failed: returning message to sender" from <>
I have set and checked through DKIM, SPF, DMARC. But the problem remains.
Have any idea to solve this question?
Related
I have Odoo 10 working since last 4 years. The Scheduled actions have been working fine until 7th May 2021.
Server Specs :
CPU - 4
Ram 16 GB
Ubuntu
The database name is : kwspl
In the server log, I find the following lines :
File "/opt/odoo/odoo-server/addons/bus/controllers/main.py", line 35, in poll
raise Exception("bus.Bus unavailable")
Exception: bus.Bus unavailable
2021-05-24 15:50:54,391 2376 INFO kwspl werkzeug: 127.0.0.1 - - [24/May/2021 15:50:54] "POST /longpolling/poll HTTP/1.1" 200 -
**2021-05-24 15:50:56,701 2381 DEBUG ? odoo.service.server: WorkerCron (2381) polling for jobs
2021-05-24 15:50:56,702 2381 DEBUG ? odoo.service.server: WorkerCron (2381) 'kwspl' time:0.001s mem: 233352k -> 233352k (diff: 0k)
2021-05-24 15:51:03,660 2382 DEBUG ? odoo.service.server: WorkerCron (2382) polling for jobs
2021-05-24 15:51:03,662 2382 DEBUG ? odoo.service.server: WorkerCron (2382) 'kwspl' time:0.002s mem: 233352k -> 233352k (diff: 0k)**
2021-05-24 15:51:04,530 2379 DEBUG kwspl odoo.modules.registry: Multiprocess signaling check: [Registry - 614 -> 614] [Cache - 57570 -> 57570]
2021-05-24 15:51:04,532 2379 ERROR kwspl odoo.http: Exception during JSON request handling.
Traceback (most recent call last):
File "/opt/odoo/odoo-server/odoo/http.py", line 640, in _handle_exception
return super(JsonRequest, self)._handle_exception(exception)
File "/opt/odoo/odoo-server/odoo/http.py", line 677, in dispatch
result = self._call_function(**self.params)
The odoo.conf is as below :
[options]
addons_path = /opt/odoo/odoo-server/addons,/opt/odoo/custom/addons
admin_passwd = ******
csv_internal_sep = ,
data_dir = /opt/odoo/.local/share/Odoo
#db_filter = kwspl
db_host = False
db_maxconn = 64
#db_name = False
db_name = 'kwspl'
db_password = False
db_port = False
db_template = template1
db_user = odoo
dbfilter = ^kwspl$
demo = {}
email_from = False
geoip_database = /usr/share/GeoIP/GeoLiteCity.dat
import_partial =
limit_memory_hard = 4684354560
limit_memory_soft = 4147483648
limit_request = 8192
limit_time_cpu = 420
limit_time_real = 180
limit_time_real_cron = -1
list_db = False
log_db = False
log_db_level = warning
#log_handler = :INFO
log_level = debug
logfile = /var/log/odoo/odoo-server.log
logrotate = False
longpolling_port = 8072
max_cron_threads = 2
osv_memory_age_limit = 1.0
osv_memory_count_limit = False
pg_path = None
pidfile = None
proxy_mode = True
reportgz = False
server_wide_modules = web,web_kanban
smtp_password = False
smtp_port = 25
smtp_server = localhost
smtp_ssl = False
smtp_user = False
syslog = False
test_commit = False
test_enable = False
test_file = False
test_report_directory = False
translate_modules = ['all']
unaccent = False
without_demo = False
workers = 4
xmlrpc = True
#xmlrpc_interface =
xmlrpc_port = 8069
If I change the following paramenters in odoo.conf
db_name = False
dbfilter = ^%d$
The following lines are seen in the log:
raise Exception("bus.Bus unavailable")
Exception: bus.Bus unavailable
2021-05-24 15:59:58,457 2574 INFO kwspl werkzeug: 127.0.0.1 - - [24/May/2021 15:59:58] "POST /longpolling/poll HTTP/1.1" 200 -
2021-05-24 16:00:03,261 2576 DEBUG ? odoo.service.server: WorkerCron (2576) polling for jobs
2021-05-24 16:00:03,316 2576 DEBUG ? odoo.tools.translate: translation went wrong for "'Selecting the "Warning" option will notify user with the message, Selecting "Blocking Message" will throw an exception with the message and block the flow. The Message has to be written in the next field.'", skipped
2021-05-24 16:00:03,376 2576 WARNING ? odoo.addons.base.ir.ir_cron: Skipping database kwspl because of modules to install/upgrade/remove.
2021-05-24 16:00:03,377 2576 INFO ? odoo.sql_db: ConnectionPool(used=0/count=0/max=64): Closed 1 connections to 'dbname=kwspl user=odoo'
2021-05-24 16:00:03,377 2576 DEBUG ? odoo.service.server: WorkerCron (2576) kwspl time:0.109s mem: 220928k -> 227084k (diff: 6156k)
2021-05-24 16:00:03,377 2576 DEBUG ? odoo.service.server: WorkerCron (2576) polling for jobs
2021-05-24 16:00:03,388 2576 INFO ? odoo.sql_db: ConnectionPool(used=0/count=0/max=64): Closed 1 connections to "dbname=\\'kwspl\\' user=odoo"
2021-05-24 16:00:03,388 2576 DEBUG ? odoo.service.server: WorkerCron (2576) 'kwspl' time:0.006s mem: 227084k -> 227084k (diff: 0k)
2021-05-24 16:00:04,190 2577 DEBUG ? odoo.service.server: WorkerCron (2577) polling for jobs
2021-05-24 16:00:04,244 2577 DEBUG ? odoo.tools.translate: translation went wrong for "'Selecting the "Warning" option will notify user with the message, Selecting "Blocking Message" will throw an exception with the message and block the flow. The Message has to be written in the next field.'", skipped
2021-05-24 16:00:04,264 2577 WARNING ? odoo.addons.base.ir.ir_cron: Skipping database kwspl because of modules to install/upgrade/remove.
2021-05-24 16:00:04,264 2577 INFO ? odoo.sql_db: ConnectionPool(used=0/count=0/max=64): Closed 1 connections to 'dbname=kwspl user=odoo'
2021-05-24 16:00:04,264 2577 DEBUG ? odoo.service.server: WorkerCron (2577) kwspl time:0.068s mem: 220928k -> 227172k (diff: 6244k)
2021-05-24 16:00:04,265 2577 DEBUG ? odoo.service.server: WorkerCron (2577) polling for jobs
2021-05-24 16:00:04,274 2577 INFO ? odoo.sql_db: ConnectionPool(used=0/count=0/max=64): Closed 1 connections to "dbname=\\'kwspl\\' user=odoo"
2021-05-24 16:00:04,275 2577 DEBUG ? odoo.service.server: WorkerCron (2577) 'kwspl' time:0.006s mem: 227172k -> 227172k (diff: 0k)
2021-05-24 16:00:05,377 2571 DEBUG kwspl odoo.modules.registry: Multiprocess signaling check: [Registry - 614 -> 614] [Cache - 57570 -> 57570]
The Scheduled Actions are no longer running while the automated Tasks are working normally.
Is this problem causing this ? -> Skipping database kwspl because of modules to install/upgrade/remove.
If this is the issue, do I check which module is the culprit?
Any Guesses?
On further investigation, I found that there was an error message in logs :
crm_rma_lot_mass_return: module not found
I tried to find this module in the current directories but could not find.
So I created an Odoo scaffolding with the same name and uploaded it on the server in one of the include directories mentioned in odoo-server.conf
This solved the problem. Odoo is now executing the Scheduled Actions.
If some faced a similar problem, I would be happy to help.
I've installed Joomla 3.4.4 (twice) with exactly the same outcome.
Problems:
- when entering ANY information into the username and password field on the back end login page, the page refreshed back to the login page without any errors or warnings on the page or in the server logs.
- the same for trying to login on the front end.
- When visiting the site, below the site title and header image a message is displayed "Error: You are not authorised to view this resource."
Both after and before installing joomla I uploaded a .user.ini to turn off magic quotes.
The configuration.php has correct settings for life site, session time out and a correct location for logs and temp files.
I've verified that the logs and tmp directory are writeable from Joomla (added code to create and write to a file in both directories).
I've checked all the modules and plugins in the database.
I've set session_save_path to a location that is writeable.
I've ruled out redirections from .htaccess.
I've enabled all messages to be displayed.
A valid cookie is sent to the browser and back to the site.
The jos1 database contains the cookies sent to the browser
The jos1 database has correct settings for both user and group
There was an warning about an unserializable object I've checked out. It's in Registry.php line 100:
public function __clone()
{
$this->data = unserialize(serialize($this->data));
}
When print_ring $this->data the following is shown:
��j Object
(
[article_layout] => _:default
[show_title] => 1
[link_titles] => 1
[show_intro] => 1
[show_category] => 1
[link_category] => 1
[show_parent_category] => 0
[link_parent_category] => 0
[show_author] => 1
[link_author] => 0
[show_create_date] => 0
[show_modify_date] => 0
[show_publish_date] => 1
[show_item_navigation] => 1
[show_vote] => 0
[show_readmore] => 1
[show_readmore_title] => 1
[readmore_limit] => 100
[show_icons] => 1
[show_print_icon] => 1
[show_email_icon] => 1
[show_hits] => 1
[show_noauth] => 0
[show_publishing_options] => 1
[show_article_options] => 1
[save_history] => 1
[history_limit] => 10
[show_urls_images_frontend] => 0
[show_urls_images_backend] => 1
[targeta] => 0
[targetb] => 0
[targetc] => 0
[float_intro] => left
[float_fulltext] => left
[category_layout] => _:blog
[show_category_title] => 0
[show_description] => 0
[show_description_image] => 0
[maxLevel] => 1
[show_empty_categories] => 0
[show_no_articles] => 1
[show_subcat_desc] => 1
[show_cat_num_articles] => 0
[show_base_description] => 1
[maxLevelcat] => -1
[show_empty_categories_cat] => 0
[show_subcat_desc_cat] => 1
[show_cat_num_articles_cat] => 1
[num_leading_articles] => 1
[num_intro_articles] => 4
[num_columns] => 2
[num_links] => 4
[multi_column_order] => 0
[show_subcategory_content] => 0
[show_pagination_limit] => 1
[filter_field] => hide
[show_headings] => 1
[list_show_date] => 0
[date_format] =>
[list_show_hits] => 1
[list_show_author] => 1
[orderby_pri] => order
[orderby_sec] => rdate
[order_date] => published
[show_pagination] => 2
[show_pagination_results] => 1
[show_feed_link] => 1
[feed_summary] => 0
)
and
��j Object
(
)
With both can be serialized but not be unserialized by PHP. I decided to comment out the line cloning the data. After this the 'Getting Started' article didn't give the error any more, but showed the article as normal. The names of the objects raise concern with me, I've never seen such names before in PHP When I print other variables. I for instance get Joomla\Register\Register Object
But this did not fix the login problem.
I'm pretty completely at a loss.
Edit:
In the database a session is created:
session_id=d984e4c528453009a9ba77ace5f58d9e,
client_id=1,
guest=1,
time=1442060444,
data=zq9ZfjiuKiKB8tyC3yEB2yREY_tylC7CD1K14M6XLIt01gwDUMTq1yY5DMVYhVUDTtPS1vmM1BFdBECdnMg0eKHlAWdZ9JwYdRNFKZl8wU_eAF61Im9d5dIy2r7Kt34upgLDzY4hmDA2EimXm-d2uKO9J6vElLCbcwFZGR2yHUq21RBQvx1wdnBMjk78z6UlI0zF9YXO6wH4WNdUlROJ85BDdhccRBrw52rzRxkpker23_nzeBK4K6nw_Eb2GN-fRAQ25PZr0XxRAtbrGAF5JvGHJDwbL9Kc34eDgOYcBwXlbCICA7be1S64K54VwYUdXZqlnqDbWUEUKb3EdvQZExY5IYRcP5McdiM2s-RYwmWpvtpIIu8VMNn1T_5c_K0gonIdngPUQeiI4r0NOncGWWt7qNjoamX8u86WVVqIVY9ufxb8Wo5INgLIUhy_TAhfBl_K5CrjNToR-13RVnBjZ1RPBeBj4hHubA2t7IZ6zbSOdPdPLbsQVYD2lsU-PjXvcN1eeqkTYNUi8U-qtfYyH-mkidMHK8hbtkS53CKGuo_D4r1K8nO16VlOI0xhK2qR2zSaykXtX_DaAkRF3AI0BvZHBrsxSc6QE2jZkRPYkdyyUnyDoyx2FTSNcPv-JrJ2uDochowEm8jyCazqIXywnmAuYb3bkMN38A7lA1IRhlrCGJY_3xpx6ZBtch4u9bUtBXuQY3E5oV5nPfL2__vW7ZADW5sUHP-e8obRo30b40iIZ3yi6DmnutdGekUi_6a9GyGVDkP3NwAoglbj5pHiLJVhfFZL54XFCuN1sHtlbismkomsx-AkOY6F27hDNCI4B4qFVX87-NF_hk2DWPqRWynCR6OCsLUPkD0apgnr-ea7KPt8qij_eu8Rn6J-RMrgHS7SE314kKoJscEXxwwnBsaoqRCwzwjEl5yHmZYS-bCocgqMGAeOf-VUmCdX-UnqGz5qgXwFBOq4tFrfJ6RQizXVdxkHml3dDmGUPMSHT9To4WXAowT8glRtMdsmZmBigM88xftj3Yr-iYTxiAwfzxPF_T8hG53d1rfPEAm0n8a_q7c6JKy9Z2HrklaqxbQzwGl6r3PwRMCaDxZ_vqq4fsPP4142I4SnAuF2WzEBFOkIyh4EUKesFV4sl4BOc19uIYhz5HSHJybh_9hlV8eB6OSHZYccvaM7F6b46Lh6g-1yDUKazCK8z-fTXHJzf6gn7UFLiWorXCQZspwK_LiW3Huv2B0HIJKxi0fEb8Zmq6juViV8LABZjG_8ZEgDvQ4InahV4k7dKIyQG3gPicaDFLqgtGnwfO2FkU3L1SUU1eAGGcyZDH15RPgfimFiwHt2A5AEPKsnh2jye3X5L53CNaB69ISY0ETVhYzXc7bGi0SADbsAVbFixXZ39IqbFyDaX3rSS0047n_riZm8xNsR6DJ2kB0R1_eWBfN_APqgynK5-Yucis4PuyblY_YwIPs2AQz5iBFgnGGCkbZDxiVG6K6CRBorqpvOPUcBN0fzyOL0xp5WfC5x3nGcbAeVOBBIh1nN7Pj1vDyjfAWGAuw5vP3g647iUmDKaxcRWZ-yGIw.,
userid = 0,
username = ''
Nothing else seems to change. The jos1_users table has an lastvisit date and time set the the date and time of installing Joomla.
No new sessions are created in the database when trying to login multiple times.
With error reporting set to development nothing is reported when visiting and trying to login the administrator back end.
When visiting the site and a few seconds later trying to login the front end this is logged:
[12-Sep-2015 07:42:19 America/Chicago] PHP Notice: unserialize() [<a href='function.unserialize'>function.unserialize</a>]: Error at offset 6 of 2159 bytes in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 82
[12-Sep-2015 07:42:19 America/Chicago] PHP Notice: unserialize() [<a href='function.unserialize'>function.unserialize</a>]: Error at offset 6 of 19 bytes in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 82
[12-Sep-2015 07:42:19 America/Chicago] PHP Strict Standards: Creating default object from empty value in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 693
[12-Sep-2015 07:42:28 America/Chicago] PHP Notice: unserialize() [<a href='function.unserialize'>function.unserialize</a>]: Error at offset 8 of 615 bytes in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 82
[12-Sep-2015 07:42:28 America/Chicago] PHP Notice: unserialize() [<a href='function.unserialize'>function.unserialize</a>]: Error at offset 8 of 19 bytes in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 82
[12-Sep-2015 07:42:28 America/Chicago] PHP Strict Standards: Creating default object from empty value in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 693
[12-Sep-2015 07:42:29 America/Chicago] PHP Notice: unserialize() [<a href='function.unserialize'>function.unserialize</a>]: Error at offset 8 of 2159 bytes in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 82
[12-Sep-2015 07:42:29 America/Chicago] PHP Notice: unserialize() [<a href='function.unserialize'>function.unserialize</a>]: Error at offset 8 of 19 bytes in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 82
[12-Sep-2015 07:42:29 America/Chicago] PHP Strict Standards: Creating default object from empty value in /home/.../public_html/.../libraries/vendor/joomla/registry/src/Registry.php on line 693
I also tried installing Drupal on the server to a different subdomain. The only thing it's able to display is these error/warnings. Again about serialization.
Notice: unserialize() [function.unserialize]: Error at offset 53 of 33869 bytes in /home/nningsh1/public_html2/test.iradis.org/includes/cache.inc on line 438
Warning: Invalid argument supplied for foreach() in /home/nningsh1/public_html2/test.iradis.org/includes/module.inc on line 213
Warning: array_keys() expects parameter 1 to be array, null given in /home/nningsh1/public_html2/test.iradis.org/includes/module.inc on line 89
Notice: unserialize() [function.unserialize]: Error at offset 53 of 33869 bytes in /home/nningsh1/public_html2/test.iradis.org/includes/cache.inc on line 438
Warning: Invalid argument supplied for foreach() in /home/nningsh1/public_html2/test.iradis.org/includes/module.inc on line 213
Warning: array_keys() expects parameter 1 to be array, null given in /home/nningsh1/public_html2/test.iradis.org/includes/module.inc on line 89
Fatal error: Call to undefined function user_access() in /home/nningsh1/public_html2/test.iradis.org/includes/menu.inc on line 636
The service provider changed PHP to not use FCGI for our domain. This fixed the problem. Both the serialization problem has been fixed, as is the login problem.
I have a functionality wherein i have to upload a large number of records from a csv file. If any one of the records is invalid, no data should be uploaded. A csv file with errors against the invalid records needs to be sent to the user who uploaded the data. I am using rails (3.2), sidekiq (2.16.1) and mysql.
All the mails (devise and custom) mails are delivered and i receive them in my gmail inbox. The above functionality worked fine before being shifted to sidekiq.
User model
#works n gets delivered in inbox
Notifier.send_welcome_mail(self).deliver
Sidekiq Worker
class UploadWorker
include Sidekiq::Worker
sidekiq_options retry: false
def perform(user_id, inspection_id)
user = User.find(user_id)
inspection = Inspection.find(inspection_id)
err = false
#check if all data is valid and upload if valid
#
...
#shows in development log but doesnt get delivered in inbox.
Notifier.delay.upload_success(user, inspection) if err
Notifier.delay.upload_failed(user, inspection) unless err
end
end
development log
Sent mail to someone#gmail.com (142ms)
Date: Wed, 13 Nov 2013 17:24:25 +0530
To: someone#gmail.com
Message-ID: <5283687179a92_203f59f273e3#gmail.mail>
Subject: ["someone#gmail.com"] Upload failed
Mime-Version: 1.0
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
sidekiq log
2013-11-13T13:21:20Z 10064 TID-1n41gu UploadWorker JID-2d2c930601caf6a62c86e142 INFO: start
2013-11-13T13:22:13Z 10064 TID-1n41gu UploadWorker JID-2d2c930601caf6a62c86e142 INFO: done: 52.858 sec
2013-11-13T13:22:13Z 10064 TID-1w7iwu Sidekiq::Extensions::DelayedMailer JID-bcae8ea4974ecfe280e411bd INFO: start
2013-11-13T13:22:14Z 10064 TID-1w7iwu Sidekiq::Extensions::DelayedMailer JID-bcae8ea4974ecfe280e411bd INFO: done: 0.858 sec
2013-11-13T13:23:51Z 10064 TID-1n41gu UploadWorker JID-03fe3dee40f6390f5cec1d93 INFO: start
2013-11-13T13:23:54Z 10064 TID-1n41gu UploadWorker JID-03fe3dee40f6390f5cec1d93 INFO: done: 2.779 sec
2013-11-13T13:23:54Z 10064 TID-1w7iwu Sidekiq::Extensions::DelayedMailer JID-44f75877c5919302c9ded4fe INFO: start
2013-11-13T13:23:54Z 10064 TID-1w7iwu Sidekiq::Extensions::DelayedMailer JID-44f75877c5919302c9ded4fe INFO: done: 0.038 sec
The issue is, only the mails from sidekiq are shown as sent in log but arent delivered. Other mails from devise n custom mail do get delivered.
Are you sure your development email settings are set correctly? Try setting the following in config/development.rb:
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_deliveries = true
config.action_mailer.smtp_settings = {
:address => '127.0.0.1',
:port => '587',
}
Im having a problem when I deploy a feature. The feature contains three bundles, and Karaf deploys well these bundles, but when they are deployed ActiveMQ starts to having problems.
The deployed bundles are simples. The "complicated" is a camel route who expose a CXF endpoint and call a endpoint mock. I just attached to this threar the .kar, the zip of that kar and my fuse log. The service is running, but the problem with activeMQ happend always
The error is always the same:
2013-05-14 15:19:48,046 | INFO | veMQ Broker: amq | ActiveMQServiceFactory$$anon$1 | ? ? | 106 - org.springframework.context - 3.1.3.RELEASE | Refreshing org.fusesource.mq.fabric.ActiveMQServiceFactory$$anon$1#33c91e: startup date [Tue May 14 15:19:48 ART 2013]; root of context hierarchy
2013-05-14 15:19:48,048 | INFO | veMQ Broker: amq | XBeanXmlBeanDefinitionReader | ? ? | 105 - org.springframework.beans - 3.1.3.RELEASE | Loading XML bean definitions from file [/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/etc/activemq.xml]
2013-05-14 15:19:48,095 | INFO | veMQ Broker: amq | DefaultListableBeanFactory | ? ? | 105 - org.springframework.beans - 3.1.3.RELEASE | Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory#1885c3a: defining beans [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,org.apache.activemq.xbean.XBeanBrokerService#0]; root of factory hierarchy
2013-05-14 15:19:48,159 | INFO | veMQ Broker: amq | PListStoreImpl | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | PListStore:[/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq/amq/tmp_storage] started
2013-05-14 15:19:48,163 | ERROR | veMQ Broker: amq | BrokerService | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Failed to start Apache ActiveMQ (amq, null). Reason: javax.management.InstanceAlreadyExistsException: org.apache.activemq:type=Broker,brokerName=amq
javax.management.InstanceAlreadyExistsException: org.apache.activemq:type=Broker,brokerName=amq
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)[:1.6.0_30]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)[:1.6.0_30]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)[:1.6.0_30]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)[:1.6.0_30]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)[:1.6.0_30]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)[:1.6.0_30]
at org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024]
at org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024]
at org.apache.activemq.broker.BrokerService.startManagementContext(BrokerService.java:2337)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024]
at org.apache.activemq.broker.BrokerService.start(BrokerService.java:543)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024]
at org.fusesource.mq.fabric.ActiveMQServiceFactory$ClusteredConfiguration$$anon$3.run(ActiveMQServiceFactory.scala:307)[128:org.jboss.amq.mq-fabric:6.0.0.redhat-024]
2013-05-14 15:19:48,164 | INFO | veMQ Broker: amq | BrokerService | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Apache ActiveMQ 5.8.0.redhat-60024 (amq, null) is shutting down
2013-05-14 15:19:48,168 | INFO | veMQ Broker: amq | TransportConnector | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Connector openwire Stopped
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | PListStoreImpl | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | PListStore:[/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq/amq/tmp_storage] stopped
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | KahaDBStore | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Stopping async queue tasks
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | KahaDBStore | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Stopping async topic tasks
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | KahaDBStore | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Stopped KahaDB
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | BrokerService | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Apache ActiveMQ 5.8.0.redhat-60024 (amq, null) uptime 0.010 seconds
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | BrokerService | ? ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Apache ActiveMQ 5.8.0.redhat-60024 (amq, null) is shutdown
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | ActiveMQServiceFactory | ? ? | 128 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Broker amq failed to start. Will try again in 10 seconds
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | ActiveMQServiceFactory | ? ? | 128 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Exception on start: javax.management.InstanceAlreadyExistsException: org.apache.activemq:type=Broker,brokerName=amq
javax.management.InstanceAlreadyExistsException: org.apache.activemq:type=Broker,brokerName=amq
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)[:1.6.0_30]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)[:1.6.0_30]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)[:1.6.0_30]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)[:1.6.0_30]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)[:1.6.0_30]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)[:1.6.0_30]
at org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024]
at org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024]
at org.apache.activemq.broker.BrokerService.startManagementContext(BrokerService.java:2337)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024]
at org.apache.activemq.broker.BrokerService.start(BrokerService.java:543)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024]
at org.fusesource.mq.fabric.ActiveMQServiceFactory$ClusteredConfiguration$$anon$3.run(ActiveMQServiceFactory.scala:307)[128:org.jboss.amq.mq-fabric:6.0.0.redhat-024]
Dropbox URL to Fuse LOG https://dl.dropboxusercontent.com/u/225304/fuse.log
Dropbox URL to .kar file https://dl.dropboxusercontent.com/u/225304/PruebaFeature-1.0-SNAPSHOT.kar
This example I used a clean Fuse. Any ideas of what is happening? i dont know if the problem is the configuration of ActiveMQ, or anything else.
This is what i recive when I list activemq in Karaf
This is when I list the broker in karaf
JBossFuse:karaf#root> activemq:query --jmxlocal
Name = KahaDBPersistenceAdapter[/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq/kahadb]
brokerName = amq
Transactions = []
Size = 13411
InstanceName = KahaDBPersistenceAdapter[/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq/kahadb]
Data = [1]
type = Broker
Service = PersistenceAdapter
brokerName = amq
service = Health
CurrentStatus = Good
type = Broker
brokerName = amq
connector = clientConnectors
type = Broker
StatisticsEnabled = true
connectorName = openwire
destinationName = ActiveMQ.Advisory.MasterBroker
MemoryUsageByteCount = 0
DequeueCount = 0
type = Broker
destinationType = Topic
Name = ActiveMQ.Advisory.MasterBroker
MinEnqueueTime = 0
MaxAuditDepth = 2048
AverageEnqueueTime = 0.0
InFlightCount = 0
MemoryLimit = 67108864
brokerName = amq
EnqueueCount = 1
MaxEnqueueTime = 0
MemoryUsagePortion = 1.0
ProducerCount = 0
UseCache = true
BlockedProducerWarningInterval = 30000
AlwaysRetroactive = false
Options =
MaxProducersToAudit = 64
PrioritizedMessages = false
ConsumerCount = 0
ProducerFlowControl = true
Subscriptions = []
QueueSize = 0
MaxPageSize = 200
DispatchCount = 0
MemoryPercentUsage = 0
ExpiredCount = 0
TopicSubscribers = []
TemporaryQueues = []
Uptime = 1 minute
TemporaryTopicSubscribers = []
MemoryPercentUsage = 0
BrokerVersion = 5.8.0.redhat-60024
StatisticsEnabled = true
TotalDequeueCount = 0
TopicProducers = []
QueueSubscribers = []
Topics = [org.apache.activemq:type=Broker,brokerName=amq,destinationType=Topic,destinationName=ActiveMQ.Advisory.MasterBroker]
TotalMessageCount = 0
SslURL =
TemporaryQueueSubscribers = []
BrokerName = amq
DynamicDestinationProducers = []
Persistent = true
DataDirectory = /home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq
Queues = []
DurableTopicSubscribers = []
TotalConsumerCount = 0
InactiveDurableTopicSubscribers = []
JobSchedulerStoreLimit = 0
TempPercentUsage = 0
MemoryLimit = 67108864
VMURL = vm://amq
OpenWireURL = tcp://fluxit-ntb-43:61616?maximumConnections=1000
JobSchedulerStorePercentUsage = 0
TotalEnqueueCount = 1
TemporaryQueueProducers = []
StompSslURL =
TemporaryTopics = []
StompURL =
Slave = false
BrokerId = ID:fluxit-ntb-43-58596-1368558172573-0:1
TotalProducerCount = 0
StorePercentUsage = 0
brokerName = amq
StoreLimit = 107374182400
TransportConnectors = {openwire=tcp://fluxit-ntb-43:61616?maximumConnections=1000}
TemporaryTopicProducers = []
TempLimit = 53687091200
QueueProducers = []
type = Broker
The features.xml in your kar is incorrect which cause this error. It has some bundle like
<bundle>mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4</bundle>
<bundle>mvn:org.apache.aries/org.apache.aries.util/1.0.0</bundle>
<bundle>mvn:org.apache.aries.proxy/org.apache.aries.proxy.api/1.0.0</bundle>
<bundle>mvn:org.apache.aries.blueprint/org.apache.aries.blueprint/1.0.1.redhat-60024</bundle>
Those bundles are very fundamental for the container and already get installed by container by default.
It shouldn't be in your features.xml, or if they're there, you should have
resolver="(obr)" for feature and dependency="true" for those bundle so that OBR resolver can kick in to prevent install redundant bundles.
Moreover, the
<bundle>mvn:org.apache.aries.blueprint/org.apache.aries.blueprint/1.0.1.redhat-60024</bundle>
is invalid for aries.blueprint 1.0.x, it should be
<bundle dependency="true" start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.api/1.0.1.redhat-60024</bundle>
<bundle dependency="true" start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.0.1.redhat-60024</bundle>
<bundle dependency="true" start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.1.redhat-60024</bundle>
instead. Otherwise you will see errors like
ERROR: Bundle org.apache.aries.blueprint [251] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.apache.aries.blueprint.ext.impl.ExtNamespaceHandler cannot be cast to org.apache.aries.blueprint.NamespaceHandler)
java.lang.ClassCastException: org.apache.aries.blueprint.ext.impl.ExtNamespaceHandler cannot be cast to org.apache.aries.blueprint.NamespaceHandler
This means you have two conflict aries.blueprint bundle installed in your container which messed up almost everything.
In a summary, change your features.xml in your kar like
<?xml version="1.0" encoding="UTF-8"?>
<features>
<feature name='tosMock' version='1.0.0-SNAPSHOT'>
<bundle>mvn:com.tecplata.esb.services/tosMock/1.0.0-SNAPSHOT</bundle>
</feature>
<feature name='esb-entities' version='1.0.0-SNAPSHOT'>
<bundle>mvn:com.tecplata.esb/esb-entities/1.0.0-SNAPSHOT</bundle>
</feature>
<feature name='vesselsService-sei' version='1.0.0-SNAPSHOT'>
<feature version='1.0.0-SNAPSHOT'>esb-entities</feature>
<bundle>mvn:com.tecplata.esb.services.sei/vesselsService-sei/1.0.0-SNAPSHOT</bundle>
</feature>
<feature name='vesselsVisitorService' version='1.0.0-SNAPSHOT'>
<bundle>mvn:org.apache.camel/camel-core/2.10.0.redhat-60024</bundle>
<feature version='1.0.0-SNAPSHOT'>vesselsService-sei</feature>
<bundle>mvn:com.tecplata.esb.services/vesselsVisitorService/1.0.0-SNAPSHOT</bundle>
</feature>
</features>
can make it work.
Freeman
The user has cross posted the same questions in many places. When you do this please tell us, as the conversation is the scattered.
Being active discussed here:
http://fusesource.com/forums/thread.jspa?threadID=4797&tstart=0
But also posted here:
https://community.jboss.org/thread/228200
I am trying to send mail using sendmail settings but i am not receiving the mail I can see the mail sent in development log.
config/application.rb
config.action_mailer.delivery_method = :sendmail
config.action_mailer.sendmail_settings = {
:location => '/usr/sbin/sendmail',
:arguments => '-i -t'
}
config.action_mailer.perform_deliveries = true
config.action_mailer.raise_delivery_errors = true
mailers/Notifier.rb
class Notifier < ActionMailer::Base
default :from => "deepika#xxx.com"
def welcome_email
mail(:to => "deepika#xxx.com", :subject => "Welcome to My Site test mail")
end
end
And i am calling Notifier.welcome_email.deliver from index method.
I can see log
Sent mail to deepika#xxx.com (339ms)
Date: Wed, 10 Apr 2013 15:16:33 +0530
From: deepika#xxx.com
To: deepika#xxx.com
Message-ID: <516534f983356_30f3262c7c84610d2#cybage-virtual-machine.mail>
Subject: Welcome to My Site test mail
Mime-Version: 1.0
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
<p>Thanks for joining and have a great day!</p>
But i am not receiving mail.
when i do service sendmail status i am getting
MSP: is run via cron (20m)
MTA: 123995 /usr/sbin/sendmail-mta -Am -L sm-mta -bd -q10m
UID PID PPID C STIME TTY TIME CMD
root 123995 1 0 15:36 ? 00:00:00 sendmail: MTA: accepting connections
Daemon Status: (process 132996) Queue runner
Current number of children: 1
QueueDir free disk space (in blocks): 285222800
Load average: 1
Child Process 139595 Status: accepting connections
Child Process 144035 Status: console socket child
QUE: Same as MTA
Also when i do vi /var/mail/root, I am getting following
This is a MIME-encapsulated message
--r3A9kDux012954.1365587178/cybage-virtual-machine.cybage.com
The original message was received at Wed, 10 Apr 2013 15:02:21 +0530
from localhost
with id r3Adsdsd9WLU5012559
----- The following addresses had permanent fatal errors -----
<deepika#xxx.com>
(reason: Client was not authenticated)
----- Transcript of session follows -----
... while talking to mail.xxx.com.:
>>> MAIL From:<> SIZE=268814
<<< 530 5.7.1 Client was not authenticated
Service unavailable
Can you please tell me what is the reason behind not receiving mail.